This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: New libtool is in the GCC and Src trees.
- From: Mike Stump <mrs at apple dot com>
- To: libtool at cwilson dot fastmail dot fm
- Cc: Steve Ellcey <sje at cup dot hp dot com>, toa at pop dot agri dot ch, jjohnstn at redhat dot com, bonzini at gnu dot org, newlib at sourceware dot org, aoliva at redhat dot com, gcc-patches at gcc dot gnu dot org, gdb-patches at sourceware dot org, binutils at sourceware dot org
- Date: Thu, 24 May 2007 15:13:45 -0700
- Subject: Re: New libtool is in the GCC and Src trees.
- References: <200705242032.NAA13355@hpsje.cup.hp.com> <1180041270.4254.1191675307@webmail.messagingengine.com>
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.