public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Greg Schafer <gschafer@zip.com.au> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/9479: ld --version parsing in gcc configury fails on latest FSF binutils-2.13.2.1 Date: Fri, 07 Feb 2003 02:26:00 -0000 [thread overview] Message-ID: <20030207022601.13337.qmail@sources.redhat.com> (raw) The following reply was made to PR other/9479; it has been noted by GNATS. From: Greg Schafer <gschafer@zip.com.au> To: gcc-gnats@gcc.gnu.org Cc: gcc-bugs@gcc.gnu.org Subject: Re: other/9479: ld --version parsing in gcc configury fails on latest FSF binutils-2.13.2.1 Date: Fri, 7 Feb 2003 13:24:38 +1100 On Fri, Feb 07, 2003 at 01:14:55PM +1100, Greg Schafer wrote: > As of this writing, the current FSF binutils release is still 2.23.2.1 so > people using that version with gcc-3.3 & 3.4 are building subtley broken > gcc's. Of course, I meant, "is still 2.13.2.1". Greg
next reply other threads:[~2003-02-07 2:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-07 2:26 Greg Schafer [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-01 5:26 Greg Schafer 2003-02-07 2:16 Greg Schafer 2003-01-28 15:26 Greg Schafer 2003-01-28 14:36 gschafer
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=20030207022601.13337.qmail@sources.redhat.com \ --to=gschafer@zip.com.au \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /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: linkBe 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).