lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LilyPond in Debian


From: Urs Liska
Subject: Re: LilyPond in Debian
Date: Tue, 12 Sep 2017 11:38:17 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1

Hi Knut,

thank you for the script.


Am 12.09.2017 um 09:34 schrieb Knut Petersen:
>
>> Hm, will I be able to get a system where I can build LilyPond again?
>
> Urs, building guile 1.8 is a pretty trivial and fast process. Just do
> it and don't care about debian

OK, I see how you build Guile directly into the LilyPond build
directory, and building Guile worked on first attempt.

I notice that upon each execution of the script Guile will be erased and
rebuilt from scratch. Am I right to assume that I could skip this step
for following builds?
And more, can't I build Guile once, into some other directory and rather
than rebuilding it each time place a symlink into the LilyPond
installation directory? This would be very useful as I tend to have
multiple builds in parallel.

>
>> 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)
>
> Attached you'll find a script that builds guile and lilypond from
> local copies of their git repositories.
> Obviously you'll have to adapt some paths defined and and used in the
> script (LILYSOURCE, GUILESOURCE, LILYROOT) first.
>

I did so (and commented out make doc for now). First compilation failed
due to missing dblatex, but the second one failed with an error I didn't
really understand. Attached you'll find the tail of the build log - any
ideas what is wrong and what I can do?

Best
Urs

> Knut

Attachment: build_error
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]