2 This documents serious bugs
4 Send bug reports to bug-gnu-music@gnu.org. For help and questions use
5 help-gnu-music@gnu.org and gnu-music-discuss@gnu.org. Please consult
6 the faq before mailing your problems.
12 [LinuxPPC-R5, egcs-1.1.2-12c]
14 Serious egcs-1.1.2-12c (stock LinuxPPC R5) bug on ppc:
18 Bug report filed, fixed in egcs-1.1.2-12f or gcc-2.95-0a.
19 Although we've currently got a workaround in place, the compiler
20 is buggy; you should upgrade:
22 ftp://dev.linuxppc.org/users/fsirl/R5/RPMS/ppc/
25 [LinuxPPC-R4, egcs-1.0.2]
27 All compiling with -O2 is suspect, in particular guile-1.3, and
28 Lily herself will break.
33 A binary RPM of Guile 1.3 has been distributed from the LilyPond ftp
34 site. This binary was made in RedHat 5.x, and it will fail if this
35 RPM is used with RedHat 6.x.
39 Guile 1.3.2 is buggy in several respects. Do not use it for LilyPond.
43 Lilypond 1.1.35-1.1.51,...: Wierd errors in guile scm_gc_mark ()
48 Some bugs may be captured in input/bugs/*y
50 [Linux i386, RedHat 5.2 with updates to 6.0]
54 configure --disable-checking --enable-printing --disable-optimise --disable-debugging
56 results in core dumps, during parsing of init files. Cause unknown.
59 --enable-checking and --enable-optimize
63 LilyPond occasionally crashes while parsing the initialisation files.
64 This is a very obscure bug, and usually entering the commandline
65 differently "fixes" it.
71 lilypond -I. ./input.ly
78 __libc_malloc (bytes=16384)
80 yyFlexLexer::yy_create_buffer ()
81 Includable_lexer::new_input (this=0x8209a00, s={strh_ = {
84 This behaviour has been observed with machines that have old libg++
85 versions (LinuxPPC feb '98, RedHat 4.x).