Neil Jerram <[email protected]> writes: >[email protected] (Riku Saikkonen) writes: >> (call-with-new-thread (lambda () 1)): >> standard input:1:1: Function not implemented ... >> It took me quite a while to get from "Function not implemented" to >> discovering that the Debian package has threads disabled, so a >> Debian-specific documentation of the change would be very useful. >Can you say specifically what you'd like to see happen instead? >Unless you only mean documentation in a Debian-specific file, I don't >see why it should be Debian-specific. For example, perhaps we >(upstream) could change that error message to add "because Guile was >built without threads support".
Hmm, yes, something like that would be good. I guess such a message would have been enough for me to start looking at how the Debian package was compiled. Perhaps guile --version or some similar option could also report the options it was compiled with (regarding enabled or disabled features), though this may be a bit more difficult to implement. >The thread-related bug was complicated (to do with locked mutexes and >forking), and I understand that it would also be complicated (because >of ABI compatibility) to re-enable threads within the series of >guile-1.8 packages. I think our best hope in practice is just to make >sure that we have threads enabled (and all working!) again in the next >major Guile release (2.0, expected sometime this year). Ok. -- -=- Rjs -=- [email protected], [email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
