Re: Bug#384565: [Monotone-devel] Re: Bug#384565: monotone - FTBFS: Build killed with signal 15

[Roman Zippel]

Hi,

On Tue, 21 Nov 2006, Shaun Jackman wrote:

> It appears the BOOST_SP_DISABLE_THREADS is the source of monotone's
> cross-platform issues on Debian. Namely, that monotone fails to run
> (deadlock) on s390, hppa, sparc, mips, and mipsel, but runs fine on
> i386, amd64, ia64, alpha and powerpc [1].
> 
> [1] http://buildd.debian.org/build.php?pkg=monotone
> 
> One suggested workaround (by Roman Zippel above) is to remove
> -DBOOST_SP_DISABLE_THREADS. The ChangeLog indicates that Nathaniel
> added this feature on 2005-09-30.
> 
> So, my questions for the monotone mailing list are...
> 
> 1. Is this more likely a bug in Boost or a bug in monotone?
> 2. Is it reasonable to workaround this bug by removing
> -DBOOST_SP_DISABLE_THREADS?
> 3. Is it worth going to the extra effort to only define
> -DBOOST_SP_DISABLE_THREADS on the platforms for which it works? I'll
> consider this last option if it means a performance improvement of at
> least, say arbitrarily, a factor of two or so.

I think this should include the boost maintainer, there has to be some way 
to safely select the proper compile flags. At least the Debian packages 
provide a threaded and non-threaded version, but the .so link points to 
the threaded version by default.
If both versions are supposed to be usable equally for non-threaded 
application it suggest a bug in boost...
Anyway, until there is some mechanism to select this safely, it's probably 
better to compile the application with the same flags as the library was.

bye, Roman