Rob Browning <[EMAIL PROTECTED]> writes: > Though not conclusive, these results, when combined with the gdb > backtrace I posted earlier showing the blockage in scm_gc() while > trying to lock a a mutex, seem to suggest that the remaining problem > is thread related.
On a related topic, in order for Guile 1.8 to make it into Debian etch (the upcoming stable release), we're essentially out of time to fix this problem. Because of this I'm contemplating uploading the initial Guile 1.8 packages with --with-threads=no. Does anyone see any major problems with this stopgap? It seems better to have Guile 1.8 in etch without threads than not to have it at all. Note that this issue doesn't just affect Guile. It's my understanding that unless Guile 1.8 packages are uploaded very soon, the newer version of lilypond won't make it into etch either. -- Rob Browning rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel
