From: Daniel Jacobowitz <drow@false.org>
To: Greg Schafer <gschafer@zip.com.au>
Cc: binutils@sources.redhat.com
Subject: Re: ld testsuite breaks with latest GCC-4.0
Date: Sun, 02 Jan 2005 05:11:00 -0000 [thread overview]
Message-ID: <20050102051144.GA8032@nevyn.them.org> (raw)
In-Reply-To: <20050102044451.GA24007@tigers-lfs.nsw.bigpond.net.au>
On Sun, Jan 02, 2005 at 03:44:51PM +1100, Greg Schafer wrote:
> Clearly, changes will be needed. I'm not sure what the best solution is but
> I have a feeling that it will probably involve:
>
> `gcc -dumpspecs'
>
> but that might have the potential to break older GCC's. Dunno.
That should work, as far back as I know of.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2005-01-02 5:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 4:45 Greg Schafer
2005-01-02 5:11 ` Daniel Jacobowitz [this message]
2005-01-02 6:24 ` [PATCH] " Greg Schafer
2005-01-03 20:51 ` James E Wilson
2005-01-04 10:30 ` Nick Clifton
2005-01-04 10:43 ` Jakub Jelinek
2005-01-04 22:47 ` Greg Schafer
2005-01-06 12:25 ` Greg Schafer
2005-01-10 14:58 ` Nick Clifton
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=20050102051144.GA8032@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=gschafer@zip.com.au \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).