release: 1.2.7

[lilypond.git] / BUGS

diff --git a/BUGS b/BUGS
index cebc3c73e6318bab0db852ce977c1020faae821d..8fb51c7c21fa12ffe0da9e401c21949f834abb86 100644 (file)
--- a/BUGS
+++ b/BUGS
@@ -5,6 +5,8 @@ Send bug reports to bug-gnu-music@gnu.org.  For help and questions use
 help-gnu-music@gnu.org and gnu-music-discuss@gnu.org.  Please consult
 the faq before mailing your problems.
 
+
+
 ********
 
 [LinuxPPC-R5, egcs-1.1.2-12c]
@@ -25,12 +27,17 @@ is buggy; you should upgrade:
 All compiling with -O2 is suspect, in particular guile-1.3, and
 Lily herself will break.
 
+
 [Linux i386]
 
 A binary RPM of Guile 1.3 has been distributed from the LilyPond ftp
 site.  This binary was made in RedHat 5.x, and it will fail if this
 RPM is used with RedHat 6.x.
 
+[GUILE 1.3.2]
+
+Guile 1.3.2 is buggy in several respects. Do not use it for LilyPond.
+
 [LinuxPPC, egcs-1.1b]
 
 Lilypond 1.1.35-1.1.51,...:  Wierd errors in guile scm_gc_mark ()
@@ -78,18 +85,3 @@ 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.