New libtool is in the GCC and Src trees.

[Andreas Tobler]

Mike Stump wrote:
> On May 24, 2007, at 2:14 PM, libtool@cwilson.fastmail.fm wrote:
>> Instead of fixing gcc's local copy, shouldn't this fix -- or a better 
>> one -- instead be submitted to libtool, and then gcc can resync?  (At 
>> least in the medium-to-long term.  For an immediate and temporary fix 
>> for a broken build, as long as it IS temporary...)
> 
> I agree.  I'm happy to have the hack in gcc so that we don't have gcc 
> not building and testing for the next month, but really, those options 
> should work on the compiler.  If someone is passing them to the linker, 
> well, that's wrong.  If to the compiler, I don't quite see what went 
> wrong, and no one said what went wrong.  Cleaverly, I was waiting on 
> other recent breakages to go away before updating, so I didn't see what 
> went wrong.
> 

/head/testbin-single/lib/libltdl.3.dylib -Wl,-compatibility_version 
-Wl,5 -Wl,-current_version -Wl,5.1
/usr/bin/ld: unknown flag: -compatibility_version
collect2: ld returned 1 exit status

And Paolo, your suggestion doesn't work. Same error.

So, do I follow correctly to put my patch into ltmain.sh on gcc?

I just want to unbreak gcc bootstrap.

Oh, and have a look into ltmain.sh on 4.2 branch... ok, I guess I put it 
in, but when I did that I synced from libtool cvs back in 03.

Andreas