Re: GCC 3.2 transition
Colin Watson <cjwatson@debian.org> writes:
> That problem shouldn't arise if the hack is done the other way
> round: new libraries go to /usr/lib/gcc3.2, say, in cases where the
> ABI differs. It does mean we can never get rid of it, but if the C++
> ABI changes in later versions of G++ then we may have to repeat this
> transition in future anyway.
The sad fact is, this may actually turn out to be the most sensible
solution, given that, like any standard, there are grey areas, and the
day before 3.2's release, the gcc team found just such a grey area
where gcc's implementation differed from Intel's, although it agreed
with HP's.
Mike.
Reply to: