hi,
i installed 2.3.13 on a separate hard drive last night and ran the same
crashing lilypond file.
it crashed there too, with slightly different output (i think?: no
"signal 6"). (using v. 2.3.13 on mac OS 10.3). the terminal output is
below. i forgot to install it with -keep-build-dir, but wil
- Open
/sw/fink/dists/unstable/main/finkinfo/text/lilypond-unstable.info with
the text editor of your choice.
i figured, since i'm using 2.2.6 (current stable) that i should change
the lilypond.info file in the /dists/stable/(etc.) file instead,
correct?
in that file i added the " --disable-op
On Sep 2, 2004, at 2:08 PM, Sean Reed wrote:
Can you repeat, but build without -O2 ?
do you mean run lilypond with the "-o" option?
or do you mean rebuild the whole of lilypond again? how do i build
without -O2?
- Open
/sw/fink/dists/unstable/main/finkinfo/text/lilypond-unstable.info with
the te
Can you repeat, but build without -O2 ?
do you mean run lilypond with the "-o" option?
or do you mean rebuild the whole of lilypond again? how do i build
without -O2?
(i didn't find that option anywhere in the fink man).
Please keep this discussion on the list.
(i assume you mean to send to bug-l
Hi,
Can you repeat, but build without -O2 ?
Please keep this discussion on the list.
[EMAIL PROTECTED] writes:
> hi matthias.
>
> i've rebuilt lilypond using the -keep-build-dir command and used the
> gdb commands as han-wen suggested. below you will find the terminal
> output of the gdb, a
I can't reproduce it (using 2.2.5 on Debian/testing). Can you send the
complete output of lilypond --verbose ?
Also, is it possible for you to see if the problem is still there in 2.2.6 or
2.3.x as well?
Erik
On Saturday 28 August 2004 18.14, Sean Reed wrote:
> dear lilypond bug control,
>
> b
dear lilypond bug control,
below is a copy of the code i'm using on macos 10.3.5 with lilypond
2.2.5 which results in this crash and error message:
../flower/include/array.hh:149: failed assertion `i >=0&&i
lilypond: error: LilyPond crashed (signal 6).
lilypond: error: Please submit a bug report t