[EMAIL PROTECTED] writes:
> I built gcc 3.2.3 and tried that for lilypong 1.8.1. It worked just
> fine. Actually, I tried 3.3.1 first, which does not work, THEN I tried
Can you send a bugreport?
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
Actually, the configure script stopped me from using it. Is that the
intended behavior?
On Tue, 2003-08-26 at 10:24, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > I built gcc 3.2.3 and tried that for lilypong 1.8.1. It worked just
> > fine. Actually, I tried 3.3.1 first, which does n
I built gcc 3.2.3 and tried that for lilypong 1.8.1. It worked just
fine. Actually, I tried 3.3.1 first, which does not work, THEN I tried
gcc 3.2.3. At any rate, I'm very happy with the result. Lilypond is
fantastic.
On Tue, 2003-08-26 at 07:01, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] wri
[EMAIL PROTECTED] writes:
> Didn't 1.6.6 have that silly bug in the font naming so that
> you couldn't get correct PDF files. I don't understand what
> the problem could have been with 1.6.10 (or 1.6.12) but
I also don't understand, since nothing fundamental changed between the
releases, but the c
Didn't 1.6.6 have that silly bug in the font naming so that
you couldn't get correct PDF files. I don't understand what
the problem could have been with 1.6.10 (or 1.6.12) but
I would definitely recommend 1.6.8 or newer to be able to
get correct PDF files.
/Mats
Han-Wen Nienhuys wrote:
[EMAIL P
[EMAIL PROTECTED] writes:
> Hmm, I can't really. I am able to use gcc 3.0.4 (unsuccessfully), but,
> beyond that, it's a pretty major update to the system.
>
> The weird thing is, I get the compilation problem even with the stock
> gcc and libc that come with the Redhat 7.3 distro. I figure it
Hmm, I can't really. I am able to use gcc 3.0.4 (unsuccessfully), but,
beyond that, it's a pretty major update to the system.
The weird thing is, I get the compilation problem even with the stock
gcc and libc that come with the Redhat 7.3 distro. I figure it's got to
be something else, then, s
[EMAIL PROTECTED] writes:
> I get the same error when I try to compile either 1.6.12 or 1.8.1:
>
> mv out/lilypond.texi out/lilypond.nexi
> chmod -w out/lilypond.nexi
> makeinfo --output=./out/lilypond.info out/lilypond.nexi
> cd ./out && /home/edwards/tarballs/lilypond-1.6.12/lily/out/lilypond
>
I get the same error when I try to compile either 1.6.12 or 1.8.1:
mv out/lilypond.texi out/lilypond.nexi
chmod -w out/lilypond.nexi
makeinfo --output=./out/lilypond.info out/lilypond.nexi
cd ./out && /home/edwards/tarballs/lilypond-1.6.12/lily/out/lilypond
--verbose
/home/edwards/tarballs/lilypon
