This documents serious bugs 

********

[LinuxPPC-R5, egcs-1.1.2-12c]

Serious egcs-1.1.2-12c (stock LinuxPPC R5) bug on ppc:

	*dest++ = *src++;

Bug report filed, fixed in egcs-1.1.2-12f.
Although we've currently got a workaround in place, the compiler
is buggy; you should upgrade:

	ftp://dev.linuxppc.org/users/fsirl/R5/RPMS/ppc/ 


[LinuxPPC-R4, egcs-1.0.2]

All compiling with -O2 is suspect, in particular guile-1.3, and
Lily herself will break.


[LinuxPPC, egcs-1.1b]

Lilypond 1.1.35-1.1.51,...:  Wierd errors in guile scm_gc_mark ()


[All platforms] 

Some bugs may be captured in input/bugs/*y

[Linux libg++ 2.7]

LilyPond occasionally crashes while parsing the initialisation files.
This is a very obscure bug, and usually entering the commandline
differently "fixes" it.

	lilypond input.ly 

and

	lilypond -I. ./input.ly 

makes a difference

Typical stacktrace:

	SIGSEGV
	__libc_malloc (bytes=16384)
	?? ()
	yyFlexLexer::yy_create_buffer ()
	Includable_lexer::new_input (this=0x8209a00, s={strh_ = {
		:

This behaviour has been observed with machines that have old libg++
versions (LinuxPPC feb '98, RedHat 4.x).  



[Linux Intel]

A problem resembling the previous: usage of libg++.2.8.x with the
wrong version of libc results in a coredump from the scanner while
reading the init files.  Stacktrace:

	ios::eof (this=0x0)
	
	yyFlexLexer::LexerInput (this=0x8294848, buf=0x82955f0 "", max_size=8192)
	yyFlexLexer::yy_get_next_buffer (this=0x8294848)
	My_lily_lexer::yylex (this=0x8294848) 

Fix: follow the install instructions of libg++: match the right
library versions.