[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: |
James Lowe |
Subject: |
Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?' |
Date: |
Tue, 22 Jan 2019 14:40:37 +0000 (GMT) |
Hello,
Sorry to top post but I have had the same error as Thomas using my 'work'
instance of Ubuntu 16.04 - at home I also use 16.04.
I try to keep the two 'OSes' the same but recently I had to reinstall my 'work'
instance as new and now, even after applying the latest git master, I get the
same 'ementaler.otf' referrenced error that I *don't* get on my home instance.
I also, on my work instance, don't have extractpdfmark installed nor the URW++
font's that are also optional and my gs version is 9.26.
I do have extractpdfmark and URW++ fonts installed at home but I don't know
what my gs version is - I seem to recall that I might have self compiled a
later version for some reason.
I'll try to play about with my work instance to see if I can pinpoint it.
James
On Tue, 22 Jan 2019 09:56:16 +0100, Thomas Morley <address@hidden> wrote:
> Am Di., 22. Jan. 2019 um 08:24 Uhr schrieb Werner LEMBERG <address@hidden>:
> >
> > >> 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.
> > >
> > > I downgraded ghostscript to 9.26, still failing. So likely not a
> > > gs-problem.
> > >
> > > Attached the make.check.log
> >
> > Thanks. Replacing your path to lilypond with mine, then doing
> > `colorwdiff', I immediately see a different value for
> > LILYPOND_BOOK_LILYPOND_FLAGS. Looking it up with
> >
> > git grep LILYPOND_BOOK_LILYPOND_FLAGS
> >
> > brings me to file `make/lysdoc-targets.make'. Obviously, you don't
> > use `extractpdfmark', right? However, this shouldn't be a problem, at
> > least theoretically.
>
> Yep, 'extractpdfmark' is optional, so I didn't bother for now.
>
> >
> > The last command present in both my and your log file is
> >
> > gs -sDEVICE=png16m \
> > -dGraphicsAlphaBits=4 \
> > -dTextAlphaBits=4 \
> >
> > -slilypond-datadir=input/regression/out-test-baseline/share/lilypond/current
> > \
> > -r101 \
> > -dAutoRotatePages=/None \
> > -dPrinted=false \
> > -sOutputFile=/home/hermann/test-output-distance.png \
> > -dNOSAFER \
> > -dEPSCrop \
> > -q \
> > -dNOPAUSE \
> > test-output-distance.eps \
> > -c quit
> >
> > to be executed while in directory
> >
> > /home/hermann/lilypond-git/build/input/regression/out-test-baseline
> >
> > (I'll soon add a patch to make `output-distance.py' show the
> > directory) – can you execute this command manually? In the above,
> > I've already adjusted `-sOutputFile'... For me this works just
> > fine.
>
> I'm very busy today, not sure I'm able to give it a try before tomorrow
> evening.
>
> Many thanks,
> Harm
- 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, 2019/01/21
- 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 <=
- 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
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', James Lowe, 2019/01/24
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', David Kastrup, 2019/01/24
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Knut Petersen, 2019/01/24