Hello list, hello /Mats,
You wrote:
> Sorry for taking so long.
Never mind! I'm glad to hear something helping ... :-)
> First of all, I can tell you that the latest autopackage installer,
> version 2.6.4.3 from the Downloads page at lilypond.org works
> excellently on Debian stable.
In deed,
Sorry for taking so long. First of all, I can tell you that the latest
autopackage installer, version 2.6.4.3 from the Downloads page at
lilypond.org works excellently on Debian stable.
If you want to compile it yourself, you can use standard versions of
all tools, except that you need to downloa
Hello list, hello /Mats,
You wrote:
> The easiest solution for you is probably to compile the program yourself.
> I'll do it myself on Debian Sarge in the coming days and can send detailed
> instructions, but it seems that the only thing you need to compile in
> addition
> to lilypond is a newer
Mats Bengtsson writes:
> Is really the autopackage compiled against libc 2.3.4?
I'm afraid that 2.6.4 might have been. I have upgraded and patched
autopackage and made 2.6.4.1 and 2.7.14 packages available that should
work better.
http://lilypond.org/download/autopackage
Jan.
--
Jan Nieu
The easiest solution for you is probably to compile the program yourself.
I'll do it myself on Debian Sarge in the coming days and can send detailed
instructions, but it seems that the only thing you need to compile in
addition
to lilypond is a newer version of fontforge, which can be downloaded
Citerar Roland Goretzki <[EMAIL PROTECTED]>:
> Hello list, hello Erik,
>
> You wrote:
>
> > Well, a 2.6.3 .deb is in debian unstable now, so perhaps you can try that.
>
> Thank You,
> I tried, but on my sarge 3.1 there are some difficulties with
> dependencies, so this is not the way ... :-(
>
Unfortunately, this is a bit of a problem with the Debian world.
Outdated and (relatively) proven is given more importance than
up-to-date -- even if the up-to-date software is better, more stable,
and much more desirable.
Because of dependency chains, installing the official 2.6.3 .deb from
Hello list, hello Erik,
You wrote:
> Well, a 2.6.3 .deb is in debian unstable now, so perhaps you can try that.
Thank You,
I tried, but on my sarge 3.1 there are some difficulties with
dependencies, so this is not the way ... :-(
Every download (meanwhile more than five) spends over 80 minutes,
Forwarded to bug-lilypond!
Is really the autopackage compiled against libc 2.3.4? If it should
work on "almost any Linux system", then it has to be compatible with
older versions of libc. On Debian stable, for example, libc has version
2.3.2.
/Mats
Roland Goretzki wrote:
Hello list,,
I wro
On Thursday 27 October 2005 01.59, Roland Goretzki wrote:
> Hello list,,
>
> I wrote:
> > Trying a little example with
> >
> > lilypond example-1.ly
> >
> > results in an error message:
> >
> > [EMAIL PROTECTED]:~/noten/2.6.3.1/probe > lilypond example-1.ly
> > GNU LilyPond 2.6.3.1
> > [ ..
Hello list,,
I wrote:
> Trying a little example with
>
> lilypond example-1.ly
>
> results in an error message:
>
> [EMAIL PROTECTED]:~/noten/2.6.3.1/probe > lilypond example-1.ly
> GNU LilyPond 2.6.3.1
> [ ... ]
> /home/roland/.local/bin/lilypond-bin-2.6.3.1: relocation error:
>
Hello list, hello Jan,
You wrote:
> try
>apt-get install libltdl3
Thank You, this did work, but afterwards there were two other libs to
install, one after another ...
That did work also, and then lilypond --version gave a good output.
But then came the next desillusionation:
Trying a littl
12 matches
Mail list logo