Urs Liska <[email protected]> writes: > Yes, indeed better than nothing (sudo apt install lilypond => "package > lilypond has no release candidate"). > OTOH it may take some pressure off the need for a "proper" solution ... > > Hm, will I be able to get a system where I can build LilyPond again? I'm > really not fluent enough with package management, but could I install > Guile 1.8 from sid and use that for setting up my LilyPond environment? > I really don't want to use an extra virtual machine just for that. > (I don't need step-by-step instructions here, just a confirmation if it > is possible (and maybe a general pointer on how to proceed)
You just take the Guile 1.8.8 distribution (Git or tarball) to some suitable directory and do ./autogen.sh # I think ./configure --disable-error-on-warning --prefix=/opt/guile-1.8 make sudo make install and then you have to use something like CONFIG_GUILE=/opt/guile-1.8/bin/config-guile ./autogen.sh in order to configure LilyPond. Compiling LilyPond will produce an inordinate amount of warnings on current GCC. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
