Re: [libstdc++] Port-specific symbol exports, porting notes

[Phil Edwards <phil at jaj dot com>]

On Sun, Jul 06, 2003 at 09:40:12PM +0200, Andreas Jaeger wrote:
> > Not for binutils 2.14, which is apparently not being detected correctly.
> > Working on it...
> 
> But we need to support binutils 2.13 - and disabling symbol versioning
> for older binutils is not an option!

I agree, but I don't think this will be a problem for users.  (Only for
cutting-edge developers like us, for 24 hours at a time.  *grin*)

My opinion is that /by the time 3.4 is released/, binutils 2.14 will be
far more widespread than it is now.  The kind of people who install 3.4
the day it's released will already have installed 2.14.  The kind of
people who stay with 3.3 for years to come will also stay with 2.1[23]
for years to come, and symvers will continues to work for them as well.


So I submit that nearly all the folks mixing development-stage compilers
with older released binutils will be us.  But we should make an effort to
support ourselves as well; I just can't think of proper fallbacks when
2.13 is detected.  Opinions desperately solicited, although I'd rather
not remove the new functionality by reverting.


(I don't know the first 2.13.9something.foo.bar pre-release which went out
with the parser fixes included, or we could require that version instead
of 2.14.)

Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams