Re: Problems using CommonC++ with gcc 4.2

This is a multi-part message in MIME format.
--------------070804020907010305010402
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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.

Andreas Pakulat wrote:
> On 04.07.07 16:02:27, Tony White wrote:
>> Not an answer, I'm afraid.  I am facing a similar problem upgrading to
>> Debian Etch - no problems under Sarge (gcc 3.x) - but under Etch,
>> nothing compiles from the source packages. I am not enough of a c, c++
>> or gcc guru to fix it.
>>
>> Anyone any idea what the problem is with gcc 4.x, and how to solve it?
> 
> I don't have any problems with gcc 4.1 using the Debian packages for
> common c++, it only breaks with gcc 4.2. And there the problem is that
> bits/atomicity.h is not included in the c++ header family and as far as
> I can see no other header provides the same contents.
> 
> Andreas
> 

--------------070804020907010305010402
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Bayonne-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bayonne-devel

--------------070804020907010305010402--