From: Mike Stump <mrs@apple.com>
To: libtool@cwilson.fastmail.fm
Cc: Steve Ellcey <sje@cup.hp.com>,
toa@pop.agri.ch, jjohnstn@redhat.com, bonzini@gnu.org,
newlib@sourceware.org, aoliva@redhat.com,
gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
binutils@sourceware.org
Subject: Re: New libtool is in the GCC and Src trees.
Date: Thu, 24 May 2007 22:13:00 -0000 [thread overview]
Message-ID: <916D5267-3B4D-42E3-99C4-CD9A7228D466@apple.com> (raw)
In-Reply-To: <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.
next prev parent reply other threads:[~2007-05-24 22:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 17:35 Steve Ellcey
2007-05-24 18:07 ` Steve Ellcey
2007-05-24 18:46 ` Steve Ellcey
2007-05-24 20:02 ` Andreas Tobler
2007-05-24 20:33 ` Steve Ellcey
2007-05-24 21:09 ` Andreas Tobler
2007-05-24 21:14 ` libtool
2007-05-24 22:13 ` Mike Stump [this message]
2007-05-25 17:38 ` Andreas Tobler
2007-05-25 17:43 ` Paolo Bonzini
2007-05-25 17:50 ` Eric Christopher
2007-05-25 19:33 ` Andreas Tobler
2007-05-25 19:39 ` Eric Christopher
2007-05-24 20:37 ` Mike Stump
2007-05-25 0:12 ` Andrew Pinski
2007-05-28 12:49 ` Andreas Schwab
2007-05-28 19:07 ` Charles Wilson
2007-05-29 1:25 ` Peter O'Gorman
2007-05-28 13:33 ` Andreas Schwab
[not found] <m3irah6d45.fsf@fleche.redhat.com>
2007-05-25 18:21 ` Steve Ellcey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=916D5267-3B4D-42E3-99C4-CD9A7228D466@apple.com \
--to=mrs@apple.com \
--cc=aoliva@redhat.com \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jjohnstn@redhat.com \
--cc=libtool@cwilson.fastmail.fm \
--cc=newlib@sourceware.org \
--cc=sje@cup.hp.com \
--cc=toa@pop.agri.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox