Re: [Bayonne-devel] Problems using CommonC++ with gcc 4.2

[Andreas Pakulat]

On 04.07.07 11:01:29, David Sugar wrote:
> This is normally tested for in m4/ost_pthread.m4 and hence in configure.  I 
> would look there and see what happens with those configure tests to see why 
> it 
> claims it can find a bits/atomicity.h if there is actually not one.  You can 
> change the ost_pthread.m4 file and then rebuild configure by running 
> ./reconfig.

Ooops, I think I just reported a "false positive" :) common-c++
obviously detects this during configuration time and the common c++
package in Debian was compiled with gcc 4.1. gcc 4.1 ships with
bits/atomicity.h and thus the config.h file is generated to include it.
This means that when one wants to use gcc 4.2 common-c++ package has to
be rebuilt using that compiler. Alternatively undef'ing
GCC_CXX_HAVE_ATOMIC_H seems to do the job as well, at least as far as
compiling goes.

Case closed for me, but I guess not for Tony as he seems to have serious
problems using common c++ with gcc 4.x...

Andreas

-- 
You are magnetic in your bearing.