Let me explain the situation as I understand it.
First, we cannot mix g++ compiles between gcc-3.3 and gcc-4.0 because of the ABI difference.
We thought (following the documentation) that setting -fabi-version=1 would solve this. In fact, it does solve it quite nicely: if you build everything with -fabi-version=1, then you can mix gcc-3.3 and gcc-4.0 compiles with no problems. (I've done extensive testing of this.)
However, we've now discovered that gcc-3.3 compiles are not compatiable with "gcc-3.3 -fabi-version=1" compiles, contrary to the documentation.
So where does this leave us? We were trying to design a system in which users could continue to use things they had already compiled under 10.3 and combine them with new things. -fabi-version=1 won't work for this; but we also can't let them use gcc-4.0 on g++ code without rebuilding all of the dependencies.
So either we tell users to stay away from Tiger until we've properly converted to gcc-4.0, or we try to create a much more hackish version of the previously-planned 10.4-transitional tree.
-- Dave
On Apr 18, 2005, at 9:45 AM, Jean-François Mertens wrote:
On 18 Apr 2005, at 15:04, Peter O'Gorman wrote:
The only thing I can suggest is having a %p/lib/fink/override/<tree>/bin/g++
and gcc and cc,c++ as symlinks to g++-3.3 and gcc-3.3 etc and fink ensuring
that %p/lib/fink/override/<tree>/bin/ comes first in $PATH when building stuff.
not sure I understand well the difference with just using SetCC and SetCXX ?
JF
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
