Re: LilyPond in Debian

[Urs Liska]

Am 11.09.2017 um 11:23 schrieb David Kastrup:
> Urs Liska <address@hidden> 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!&nbsp;</button></p>


:-)

> make

This aborts with errors related to .texi files and ...

> sudo make install

... this too.
However, before it reports

Libraries have been installed in:
   /opt/guile-1.8/lib
After that it enters and leaves the srfi subdirectory and starts
complaining inside doc.

So I *think* Guile itself is compiled and installed correctly, but the
docs are not.
How can I easily check if the library is available? ldconfig -p | grep
guile only returns entries for Guile 2 in /lib/x86_64-linux-gnu (but
maybe ldconfig doesn't know about self-compiled libraries?)

>
> and then you have to use something like
> CONFIG_GUILE=/opt/guile-1.8/bin/config-guile ./autogen.sh
>
> in order to configure LilyPond.

I think I should not start trying this before having confirmed the
previous step.

Urs

>
> Compiling LilyPond will produce an inordinate amount of warnings on
> current GCC.
>