release: 1.2.7

[lilypond.git] / BUGS

diff --git a/BUGS b/BUGS
index 054d425246941e3b94db75c303ab66b7b7458f03..8fb51c7c21fa12ffe0da9e401c21949f834abb86 100644 (file)
--- a/BUGS
+++ b/BUGS
@@ -1,43 +1,62 @@
 
 This documents serious bugs 
 
+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.
+
+
+
 ********
 
-[Linux Intel, EGCS-1.1b]
+[LinuxPPC-R5, egcs-1.1.2-12c]
 
-Compiling with -O2 -finline-functions will cause crashes during
-parsing stage.
+Serious egcs-1.1.2-12c (stock LinuxPPC R5) bug on ppc:
 
+       *dest++ = *src++;
 
-[All platforms] 
+Bug report filed, fixed in egcs-1.1.2-12f or gcc-2.95-0a.
+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/ 
 
-When dealing with beaming that is not correct (eg quarter notes in
-beams.), you can get the following assert.  This is a serious bug, but
-a good solution is quite a lot of work.
 
-       \score{
-               \melodic{
-                       [c2 c]
-               }
-       }
+[LinuxPPC-R4, egcs-1.0.2]
 
-results in
+All compiling with -O2 is suspect, in particular guile-1.3, and
+Lily herself will break.
 
-       lilypond: ../flower/include/varray.hh:141: struct Rhythmic_grouping *& Array<Rhythmic_grouping *>::elem(int) const: Assertion `i >=0&&i<size_' failed.
 
-And this
+[Linux i386]
 
-       \score{
-               \melodic{
-                       [c]
-               }
-       }
+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.
 
-in
+[GUILE 1.3.2]
 
-       lilypond: ../flower/include/cursor.tcc:104: int Cursor<void *>::operator -(class Cursor<void *>) const: Assertion `c.ok()' failed.
-       Aborted (core dumped)
+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 ()
+
+
+[All platforms] 
 
+Some bugs may be captured in input/bugs/*y
+
+[Linux i386, RedHat 5.2 with updates to 6.0]
+
+Compiling with 
+
+       configure --disable-checking --enable-printing --disable-optimise --disable-debugging
+
+results in core dumps, during parsing of init files. Cause unknown.
+Solution: use
+
+       --enable-checking and --enable-optimize
 
 [Linux libg++ 2.7]
 
@@ -66,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.