> IIRC it's a compatibility issue. I think the LilyPond wrapper script (usually ~/bin/lilypond) has to set > the right path to the local Lilypond gs. > Basically, if LilyPond invokes the system gs it's often the wrong version.
The wrapper looks good to me: #!/bin/sh me=`basename $0` export LD_LIBRARY_PATH="/home1/myusername/lilypond/usr/lib" exec "/home1/myusername/lilypond/usr/bin/$me" "$@" [~]# ls -l /home1/myusername/lilypond/usr/lib | head total 18432 drwxr-xr-x 7 myusername myusername 4096 Jun 5 03:32 ./ drwxr-xr-x 7 myusername myusername 4096 Mar 17 2014 ../ drwxr-xr-x 3 myusername myusername 4096 Oct 6 2013 ghostscript/ drwxr-xr-x 3 myusername myusername 4096 Oct 6 2013 gio/ -rwxr-xr-x 1 myusername myusername 1030 Mar 17 2014 libasprintf.la* lrwxrwxrwx 1 myusername myusername 20 Jun 5 03:31 libasprintf.so -> libasprintf.so.0.0.0* lrwxrwxrwx 1 myusername myusername 20 Jun 5 03:21 libasprintf.so.0 -> libasprintf.so.0.0.0* -rwxr-xr-x 1 myusername myusername 6752 Mar 17 2014 libasprintf.so.0.0.0* -rw-r--r-- 1 myusername myusername 1016 Mar 17 2014 libdb-4.7.la [~]# I appreciate your help... and I admire your persistence! _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user