public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: chris@stockwith.co.uk
To: gcc-gnats@gcc.gnu.org
Subject: other/9473: configure bug. gcc/configure fails on versions of binutils
Date: Tue, 28 Jan 2003 11:36:00 -0000 [thread overview]
Message-ID: <20030128113558.20109.qmail@sources.redhat.com> (raw)
>Number: 9473
>Category: other
>Synopsis: configure bug. gcc/configure fails on versions of binutils
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Jan 28 11:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Chris Lingard
>Release: 3.2.1 but this bug is propagated in future issues
>Organization:
>Environment:
>Description:
gcc's configure fails to detect binutils 2.13.2.1. It cannot
decode version numbers with more than three fields
This causes:
checking assembler hidden support... no
>How-To-Repeat:
Just configure using binutils 2.13.2.1, instead of 2.13.2
>Fix:
Patch attached; or change gcc-3.x.x.gcc/configure to
recognize binutils version.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-diff; name="gcc-3.2.1-binutils.patch"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="gcc-3.2.1-binutils.patch"
ZGlmZiAtTmF1ciBnY2MtMy4yLjEub2xkL2djYy9jb25maWd1cmUgZ2NjLTMuMi4xL2djYy9jb25m
aWd1cmUKLS0tIGdjYy0zLjIuMS5vbGQvZ2NjL2NvbmZpZ3VyZQkyMDAyLTA5LTA2IDExOjU4OjQ4
LjAwMDAwMDAwMCArMDEwMAorKysgZ2NjLTMuMi4xL2djYy9jb25maWd1cmUJMjAwMy0wMS0yOCAx
MDo0NDoxOC4wMDAwMDAwMDAgKzAwMDAKQEAgLTcyMTYsNyArNzIxNiw4IEBACiAJIyB0aGUgZGF0
ZSBzdHJpbmcgYWZ0ZXIgdGhlIHZlcnNpb24gbnVtYmVyLgogCWxkX3Zlcj1gJGdjY19jdl9sZCAt
LXZlcnNpb24gMj4vZGV2L251bGwgfCBoZWFkIC0xYAogCWlmIGVjaG8gIiRsZF92ZXIiIHwgZ3Jl
cCBHTlUgPiAvZGV2L251bGw7IHRoZW4KLQkJbGRfdmVycz1gZWNobyAkbGRfdmVyIHwgc2VkIC1u
ICdzLF4uKlsgCV1cKFswLTldWzAtOV0qXC5bMC05XVswLTldKlwoXHxcLlswLTldWzAtOV0qXClc
KVwoWyAJXS4qXHxcKSQsXDEscCdgCisgbGRfdmVycz1gZWNobyAkbGRfdmVyIHwgc2VkIC1uICdz
LF4uKlsgIF1cKFswLTldWzAtOV0qXC5bMC05XVswLTldKlwuWzAtOV1bMC05XSpcKFx8XC5bMC05
XVswLTldKlwpXClcKFsgICAgIF0uKlx8XCkkLFwxLHAnYAorCiAJCWxkX2RhdGU9YGVjaG8gJGxk
X3ZlciB8IHNlZCAtbiAncyxeLipcKFsyLTldWzAtOV1bMC05XVswLTldXClbLV0qXChbMDFdWzAt
OV1cKVstXSpcKFswLTNdWzAtOV1cKS4qJCxcMVwyXDMscCdgCiAJCWlmIHRlc3QgMCIkbGRfZGF0
ZSIgLWx0IDIwMDIwNDA0OyB0aGVuCiAJCQlpZiB0ZXN0IC1uICIkbGRfZGF0ZSI7IHRoZW4K
next reply other threads:[~2003-01-28 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 11:36 chris [this message]
2003-01-29 14:52 ehrhardt
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=20030128113558.20109.qmail@sources.redhat.com \
--to=chris@stockwith.co.uk \
--cc=gcc-gnats@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).