This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: Patch to update libtool in GCC and Src trees
- From: Paolo Bonzini <paolo dot bonzini at lu dot unisi dot ch>
- To: Charles Wilson <libtool at cwilson dot fastmail dot fm>
- Cc: Steve Ellcey <sje at cup dot hp dot com>, binutils at sourceware dot org, gcc-patches at gcc dot gnu dot org, gdb-patches at gcc dot gnu dot org, newlib at sourceware dot org
- Date: Tue, 08 May 2007 08:15:53 +0200
- Subject: Re: Patch to update libtool in GCC and Src trees
- References: <463F6F90.4080401@cup.hp.com> <463F873D.5000706@lu.unisi.ch> <463FF2AE.3000503@cwilson.fastmail.fm>
- Reply-to: bonzini at gnu dot org
Either way, Steve's existing patch needs to be extended to do
_something_ with newlib, and that means a few more days of shakedown so
the linux-native-newlib guys can test it.
Agreed.
Ralf W. and I have been working on some refinements for cygwin/mingw
libtool in libtool's ToT over the last few weeks. They are not yet
ready, and I certainly do not want to hold back gcc progress waiting on
libtool: the 20070318 libtool ToT included in Steve's update works fine
as demonstrated above. However, now that Steve's done all or most of
the _hard_ work, what will be the policy going forward with regards to
updating external, but embedded, tools like libtool?
How often will gcc re-import the latest libtool ToT? Any chance of
another -- less disruptive! -- update before 4.THREE.0 ships?
If it were only for me, we could commit to syncing libtool ToT
periodically at least until libtool 2.0 is out. But I suspect that to
convince everybody, libtool would need a more precise notion of
stable-ness. After that, it will be the usual mess, the same as for
Autoconf and Automake... :-)
Paolo