[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new
From: |
Werner LEMBERG |
Subject: |
Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?' |
Date: |
Mon, 21 Jan 2019 10:17:15 +0100 (CET) |
>> > Failed with:
>> >
>> > Error: /undefinedfilename in --file--
>> > Operand stack:
>> >
>> > (input/regression/out-test-baseline/share/lilypond/current/fonts/otf/emmentaler-20.otf)
>>
>> I can't reproduce that. I followed exactly your recipe (but
>> omitting `-j3 CPU_COUNT=3'), and it works just fine for me on my
>> openSUSE box.
>
> Meanwhile I tried LilyDev-0.3 which is debian-9, 64-bit, ghostscript
> 9.20 and same gcc-version as above. No error for the make, make
> test-baseline, make check sequence.
OK.
> A ghostscript problem?
Hmm, doesn't look like one – a missing file is a missing file...
Maybe the `-j3' option? Can you repeat the whole thing without any
options for parallel computing and show us the output of
make check &> make.check.log &
please? I could then compare it directly with my log file.
Werner
- I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', pkx166h, 2019/01/19
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Werner LEMBERG, 2019/01/20
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Knut Petersen, 2019/01/20
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', pkx166h, 2019/01/20
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Thomas Morley, 2019/01/20
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Werner LEMBERG, 2019/01/20
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Thomas Morley, 2019/01/20
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?',
Werner LEMBERG <=
- Message not available
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Werner LEMBERG, 2019/01/22
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Thomas Morley, 2019/01/22
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', James Lowe, 2019/01/22
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Thomas Morley, 2019/01/22
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', pkx166h, 2019/01/22
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', James Lowe, 2019/01/23
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Thomas Morley, 2019/01/23
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', James Lowe, 2019/01/23
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Thomas Morley, 2019/01/23
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Knut Petersen, 2019/01/23