On Mon 16 Oct 2017 at 18:31:36 (+0200), Simon Albrecht wrote: > On 16.10.2017 18:28, Simon Albrecht wrote: > >On 16.10.2017 17:13, David Kastrup wrote: > >>Simon Albrecht <simon.albre...@mail.de> writes: > >> > >>>Hello everybody, > >>> > >>>I’ve just noticed a problem when compiling a medium to large score (44 > >>>pages of output) with 2.19.65: everything is fine until GS fails with > >>>the message > >>>warning: g_spawn_sync failed (0): gs: Failed to fork (Cannot allocate > >>>memory). > >>>Compiling the 3–5 page bookparts individually is no problem. > >>> > >>>Does this ring a bell with anybody? or > >>>How should I further investigate the problem? or > >>>Would anybody be interested in getting the file privately to > >>>investigate? > >>It might be worth mentioning what kind of system and which Ghostscript > >>you are seeing this problem with. > > > >Ubuntu 16.04. > >I forgot earlier to mention in the e-mail that I tried with > >$ lilypond -fps printAll.ly > >$ ps2pdf printAll.ps > >and it worked. > > $ which gs > /usr/bin/gs > $ gs --version > 9.18
Does that mean anything at the command line? I get the impression that LP juggles with LD_LIBRARY_PATH etc (unless your distribution has actually set up 2.19.65 as the system version). Cheers, David. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
