Hi Daniel!
Gentoo ships a patch that has enabled me to build against Guile 2.2.3 and run
successfully:
http://mirrors.evowise.com/gentoo-portage/media-sound/lilypond/files/lilypond-2.19.80-remove-ly-protect.patch
Well, a successful build is nice, but there are still major problems with guile
2.*
First of all: a lilypond build that uses guile 2.* is very very slow. It is not
expected that
this problem will be solved soon.
Building guile 1.8* is a trivial and fast exercise if you compare
it with the task to build lilypond.
With one small patch it is possible to build and install a guile 1.8*
that is hidden from the rest of the system but that is usable for
lilypond: If GUILELIBDIR is set to a reasonable non-standard path,
then run
sed -i "s|lt_dlinit ();|lt_dlinit (); lt_dlsetsearchpath
(\"$GUILELIBDIR\");|" libguile/dynl.c
in the guile source directory and build guile. After that execute
export LDFLAGS="-Wl,-rpath,$GUILELIBDIR"
to inform lilypond where guile 1.8 resides, build and install ilypond.
Have a look at the build script attached to
https://lists.gnu.org/archive/html/lilypond-devel/2017-09/msg00072.html
The script builds guile 1.8* and lilypond, guile is patched on the fly.
Of course it's necessary to clone the guile repository first and to
adapt some paths (LILYSOURCE, GUILESOURCE and LILYROOT)
to your needs.
cu,
Knut
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
