|
Boost : |
From: Joerg Walter (jhr.walter_at_[hidden])
Date: 2003-07-05 04:20:13
----- Original Message -----
From: "Gabriel Dos Reis" <gdr_at_[hidden]>
To: "Boost mailing list" <boost_at_[hidden]>
Sent: Monday, June 30, 2003 12:06 PM
Subject: Re: [boost] Compiler status for GCC 3.3
[...]
> | I'm not sure about this. Paul C. Leopardi and Guillaume Melquiond
already
> | reported the issue, Paul also analyzed it here
> | http://groups.yahoo.com/group/ublas-dev/message/676
> |
> | In essence: setting -fabi-version=0 should solve the problem.
>
> On the other hand if your native compiler is GCC and your system was
> not configured with that setting, then you may get into trouble --
> since you'll be mixing translation units with different ABIs.
It sounds as if GCC 3.3 itself could be affected by -fabi-version=?. If say
for example libstdc++ isn't binary compatible when build with
different -fabi-version settings don't we have two different compilers
depending on configure's -fabi-version then?
Thanks,
Joerg
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk