Johan Vromans wrote:
OOo supplies its own versions of several libraries, and sets the
LD_LIBRARY_PATH environment variable to force loading the private
libs. When starting lilypond via OOoLilyPond LD_LIBRARY_PATH is passed
to lilypond as well, and it chokes on the non-compatible version of
the libs.
I posted a simple workaround a couple of days ago.
Thanks a lot for your workaround. I think it is a good idea to
automatically append the lilypond command to the env command. Or do you
see there any problems?
regards,
Samuel
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
