Urs Liska <[email protected]> writes: > Am 11.09.2017 um 14:47 schrieb David Kastrup: >> Urs Liska <[email protected]> writes: >> >>> Am 11.09.2017 um 11:23 schrieb David Kastrup: >>>> 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 >>> This worked quite well, except I had to compile GNU MP along the way, >>> which made me stumble over this little gem of web publishing: >>> >>> <p style="text-align:center;">This site does <b>not</b>use cookies >>> <button type="button">I agree! </button></p> >>> >>> >>> :-) >>> >>>> make >>> This aborts with errors related to .texi files and ... >> Oh right. Should not have gone from memory. > > Thanks, but: > > $ git apply 0001-Fix-Texinfo-sectioning.patch
git am 0001-Fix-Texinfo-sectioning.patch git apply is for diffs, not for mail-formatted patches. No idea whether it would help, but at least you get a proper commit. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
