public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drow at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/32287] gas version style changed causes warnings with configure
Date: Mon, 21 Jan 2008 21:59:00 -0000 [thread overview]
Message-ID: <20080121214602.10580.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32287-13830@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from drow at gcc dot gnu dot org 2008-01-21 21:46 -------
Subject: Re: gas version style changed causes
warnings with configure
On Mon, Jan 21, 2008 at 09:43:09PM -0000, hjl dot tools at gmail dot com wrote:
> The second line isn't needed. I checked the following versions:
>
> ./check "GNU ld version 2.17.50.0.6-5.fc6 20061020"
> ./check "GNU ld version 2.17.50.0.12-4 20070128"
> ./check "GNU ld version 2.15.92.0.2 20040927"
> ./check "GNU ld (GNU Binutils) 2.18.50.20070913"
> ./check "GNU ld (Linux/GNU Binutils) 2.18.50.0.1.20070906"
> ./check "GNU ld (GNU Binutils) 2.17.50.20070726-12 (SUSE Linux)"
> ./check "GNU assembler (GNU Binutils for Debian) 2.17.50.20070426"
>
> and they work fine. Do you have more to add?
It will fail on any line that contains xx.yy after the binutils
version. Didn't that used to happen?
If not we can remove basically the entire test. Once the first
pattern matches the rest is mostly irrelevant.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32287
next prev parent reply other threads:[~2008-01-21 21:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 16:25 [Bug bootstrap/32287] New: Grep for "as" broken -- configure: line 14092: test: too many arguments sleb128 uleb128 rob1weld at aol dot com
2007-06-11 18:01 ` [Bug bootstrap/32287] " rob1weld at aol dot com
2007-06-11 22:25 ` [Bug bootstrap/32287] gas version style changed causs warnings with configure pinskia at gcc dot gnu dot org
2007-06-12 11:37 ` rob1weld at aol dot com
2007-07-28 0:53 ` [Bug bootstrap/32287] gas version style changed causes " pinskia at gcc dot gnu dot org
2007-07-28 0:53 ` pinskia at gcc dot gnu dot org
2007-10-10 20:47 ` haubi at gentoo dot org
2007-11-20 19:46 ` rask at gcc dot gnu dot org
2008-01-15 10:39 ` aldot at gcc dot gnu dot org
2008-01-21 20:54 ` drow at gcc dot gnu dot org
2008-01-21 21:59 ` drow at gcc dot gnu dot org [this message]
2008-01-21 21:59 ` hjl dot tools at gmail dot com
2008-01-21 22:02 ` hjl dot tools at gmail dot com
2008-01-21 23:56 ` hjl dot tools at gmail dot com
2008-01-22 13:38 ` drow at gcc dot gnu dot org
2008-01-22 13:58 ` hjl at gcc dot gnu dot org
2008-01-22 14:22 ` hjl dot tools at gmail dot com
[not found] <bug-32287-4@http.gcc.gnu.org/bugzilla/>
2012-02-03 22:48 ` pinskia at gcc dot gnu.org
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=20080121214602.10580.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: 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).