* Documentation/topdocs/INSTALL.texi (Top): Add some warnings

about guile --with-threads.  Hopefully this issue can be resolved
rsn, but maybe we should even add warnings for the standard Debian
and Red Hat packages?

* configure.in: Warn if guile is configured to use threads.  Maybe
we should make this an error (ie, add to REQUIRED list?)

diff --git a/ChangeLog b/ChangeLog
index a74d5cba5519b15d19c7b2b03165ab31c48a0b58..a820d5a90f9f80ccfde1074844f5d39b1e1a9227 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,13 @@
 2002-06-23  Jan Nieuwenhuizen  <janneke@gnu.org>
 
+       * Documentation/topdocs/INSTALL.texi (Top): Add some warnings
+       about guile --with-threads.  Hopefully this issue can be resolved
+       rsn, but maybe we should even add warnings for the standard Debian
+       and Red Hat packages?
+
+       * configure.in: Warn if guile is configured to use threads.  Maybe
+       we should make this an error (ie, add to REQUIRED list?)
+
        * config.make.in (PACKAGE_NAME):
        (PACKAGE, package):  Don't hardcode.
 

diff --git a/Documentation/topdocs/INSTALL.texi b/Documentation/topdocs/INSTALL.texi
index be3b0ca6d326684f0543d165030515f25bb85aac..bbed71b4e004422334f7301658080fbb78b973dc 100644 (file)
--- a/Documentation/topdocs/INSTALL.texi
+++ b/Documentation/topdocs/INSTALL.texi
@@ -142,7 +142,9 @@ distribution supports g++ 3.x and flex.
 @item Python (version 1.5 or newer).
 Check out @uref{http://www.python.org, the python website}.
 
-@item GUILE (version 1.4 or newer).
+@item GUILE (version 1.4 or newer), --without-threads.
+Using guile, ./configure'd --with-threads may give nasty memory
+corruption errors on large scores.
 Check out
 @uref{http://www.gnu.org/software/guile/guile.html,the GUILE webpage}.
 
@@ -208,8 +210,10 @@ following software
 @itemize @bullet
 @item @TeX{}.
 @item Xdvi and Ghostscript
-@item GUILE 1.4, or newer.  Check out
+@item GUILE 1.4, or newer, --without-threads.  Check out
 @uref{http://www.gnu.org/software/guile.html,the GUILE webpage}
+Using guile, ./configure'd --with-threads may give nasty memory
+corruption errors on large scores.
 @end itemize
 
 For running LilyPond successfully you have to help @TeX{} and MetaFont find

diff --git a/configure.in b/configure.in
index 6f70a28f4396e2b2aff561cf1aa251a83604b037..2dff4ea42d1193376ff41d2e788958433a56a427 100644 (file)
--- a/configure.in
+++ b/configure.in
@@ -65,6 +65,21 @@ fi
 AC_DEFINE_UNQUOTED(TOPLEVEL_VERSION, "${FULL_VERSION}")
 AC_DEFINE_UNQUOTED(FLOWER_VERSION, "${FULL_FLOWER_VERSION}")
 
+# Check for guile ./configure'd --with-threads
+# which shows nasty memory corruption errors.
+# Until we found the real cause, advise no to use threads
+exe=`STEPMAKE_GET_EXECUTABLE($guile_config)`
+if test -n "$exe" -a -x "$exe"; then
+    AC_MSG_CHECKING(["for guile, ./configure'd --without-threads"])
+    link=`$guile_config link`
+    if expr "$link" : '.*\(thread\)' >/dev/null 2>&1; then
+       STEPMAKE_ADD_ENTRY(OPTIONAL, "[guile, ./configure'd --without-threads (using guile with threads may give nasty memory corruption errors on large scores).]")
+       AC_MSG_RESULT([no, watch out.])
+    else
+       AC_MSG_RESULT([yes, good.])
+    fi
+fi    
+
 # Gather requirements and generate output.
 STEPMAKE_END