----- Original Message -----
From: "Phil Holmes" <m...@philholmes.net>
To: "Werner LEMBERG" <w...@gnu.org>
Cc: <d...@gnu.org>; <lilypond-devel@gnu.org>
Sent: Monday, December 24, 2018 3:17 PM
Subject: Re: GUB lilypond build fails
----- Original Message -----
From: "Werner LEMBERG" <w...@gnu.org>
To: <m...@philholmes.net>
Cc: <d...@gnu.org>; <lilypond-devel@gnu.org>
Sent: Monday, December 24, 2018 1:11 PM
Subject: Re: GUB lilypond build fails
This command seems to fail. Can you run it manually (with proper
values for $PATH, $GS_FONTPATH, and $GS_LIB) so that we can see its
output? Information about the environment variables should be
available in `lilypond-test.log'.
Any idea of what would be the proper values for those 3 environment
variables?
As mentioned above! A very long line in `lilypond-test.log' shows the
values. Looking into my
/home/wl/git/gub/target/linux-64/log/lilypond-test.log
file I see
+cd
/home/wl/git/gub/target/linux-64/build/lilypond-git.sv.gnu.org--lilypond.git-master
\
&& ulimit -m 524288 \
&& ulimit -d 524288 \
&& ulimit -v 2097152 \
&&
LILYPOND_EXTERNAL_BINARY=/home/wl/git/gub/target/linux-64/root/usr/bin/lilypond
\
PATH=\
/home/wl/git/gub/target/tools/root/usr/bin\
:/home/wl/git/gub/target/linux-64/root/usr/bin\
:$PATH MALLOC_CHECK_=2 \
LD_LIBRARY_PATH=\
/home/wl/git/gub/target/tools/root/usr/lib\
:/home/wl/git/gub/target/linux-64/root/usr/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
\
GS_FONTPATH=\
/home/wl/git/gub/target/linux-64/root/usr/share/ghostscript/9.21/fonts\
:/home/wl/git/gub/target/linux-64/root/usr/share/gs/fonts \
GS_LIB=\
/home/wl/git/gub/target/linux-64/root/usr/share/ghostscript/9.21/Resource/Init\
:/home/wl/git/gub/target/linux-64/root/usr/share/ghostscript/9.21/Resource
\
FONTCONFIG_FILE=/home/wl/git/gub/target/linux-64/root/usr/etc/fonts/fonts.conf
\
FONTCONFIG_PATH=/home/wl/git/gub/target/linux-64/root/usr/etc/fonts \
make -j4 \
CPU_COUNT=2 \
MISSING_OPTIONAL=dblatex \
test
Put the environment variables after the last `&&' into a shell script
and execute the gs command in the right directory (given as the first
`cd' command).
Werner
I'll try a build of current master.
Same problem for me.
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel