2 This documents serious bugs
6 [LinuxPPC-R5, egcs-1.1.2-12c]
8 Serious egcs-1.1.2-12c (stock LinuxPPC R5) bug on ppc:
12 Bug report filed, fixed in egcs-1.1.2-12f.
13 Although we've currently got a workaround in place, the compiler
14 is buggy; you should upgrade:
16 ftp://dev.linuxppc.org/users/fsirl/R5/RPMS/ppc/
19 [LinuxPPC-R4, egcs-1.0.2]
21 All compiling with -O2 is suspect, in particular guile-1.3, and
22 Lily herself will break.
27 Lilypond 1.1.35-1.1.51,...: Wierd errors in guile scm_gc_mark ()
32 Some bugs may be captured in input/bugs/*y
36 LilyPond occasionally crashes while parsing the initialisation files.
37 This is a very obscure bug, and usually entering the commandline
38 differently "fixes" it.
44 lilypond -I. ./input.ly
51 __libc_malloc (bytes=16384)
53 yyFlexLexer::yy_create_buffer ()
54 Includable_lexer::new_input (this=0x8209a00, s={strh_ = {
57 This behaviour has been observed with machines that have old libg++
58 versions (LinuxPPC feb '98, RedHat 4.x).
64 A problem resembling the previous: usage of libg++.2.8.x with the
65 wrong version of libc results in a coredump from the scanner while
66 reading the init files. Stacktrace:
70 yyFlexLexer::LexerInput (this=0x8294848, buf=0x82955f0 "", max_size=8192)
71 yyFlexLexer::yy_get_next_buffer (this=0x8294848)
72 My_lily_lexer::yylex (this=0x8294848)
74 Fix: follow the install instructions of libg++: match the right