Hi David, > > The import of my post was to raise the question of whether the parts > of your LP system are incompatible and, if so, whether that was > brought about by the source of your LP system (which would probably > affect many people) or just a problem in your own setup.
Well, the best I can do is say that I downloaded the most recent tarball into ~/[$lilypond-dir], ran /[$lilypond-dir]/bin/uninstall-lilypond, and then installed the new tarball with 'sh lilypond-2.19.54-1.linux-64.sh --prefix [$lilypond-dir]/'. (there's actually another option I remember having as part of the tarball install, but I can neither remember it nor find it in the console buffer or under --help). That should have installed a self-contained Lily install, yes? And I would repeat here the addendum I made to my first message: I was able to use lilypond-2.19.52 without error mid-January, and was unable to do so after updating some packages (including ghostscript). But if Lily is using her own internal invocation of ghostscript, that shouldn't even matter, right? So I'm not sure wherein the problem lies. Thanks for the help, A
_______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
