From: ts <decoux@...>
Date: 2003-12-09T00:38:41+09:00
Subject: Re: Ruby blocks... forever

>>>>> "N" == Nathaniel Talbott <nathaniel@talbott.ws> writes:

N> Now, can you or someone else help me understand what this option 
N> actually does? 

 it compile ruby with -lpthread to be sure that the thread system is
 correctly initialized.

N>                And why, if it's such a problem, it hasn't showed up 
N> before and it isn't on by default? 

 If I've well understood : it not by default because it can cause problems
 on some architecture (*BSD ???)

N>                                    Was every extension linked to 
N> pthread before doomed to lock up eventually?

 Don't expect that one day I can understand pthread :-(

 In the distribution of bdbxml, you have

# it's important to have xercesc compiled with -rnone 
# (i.e. *without* threads)

 because if xerces-c is compiled with pthread you'll see strange problems
 


Guy Decoux