public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: chris@stockwith.co.uk
To: gcc-gnats@gcc.gnu.org
Cc: mark@codesourcery.com
Subject: other/10745: Bug in gcc-3.3/gcc/configure
Date: Mon, 12 May 2003 12:21:00 -0000 [thread overview]
Message-ID: <20030512121003.29703.qmail@sources.redhat.com> (raw)
>Number: 10745
>Category: other
>Synopsis: Bug in gcc-3.3/gcc/configure
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon May 12 12:16:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Chris Lingard
>Release: GCC 3.3 Prerelease 20030506
>Organization:
>Environment:
>Description:
Handle binutils versions with 4 dot separated numbers
Fails to detect GNU binutils, when it has a four digit version
This bug was fixed on gcc-3.2.2 2003-02-03
The bug causes
checking assembler hidden support... no
and a very broken system
>How-To-Repeat:
Use binutils-2.13.2.1
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-diff; name="gcc-3.3.patch"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="gcc-3.3.patch"
ZGlmZiAtTmF1ciBnY2MtMy4zLm9sZC9nY2MvY29uZmlndXJlIGdjYy0zLjMvZ2NjL2NvbmZpZ3Vy
ZQotLS0gZ2NjLTMuMy5vbGQvZ2NjL2NvbmZpZ3VyZQkyMDAzLTA0LTA0IDEwOjE3OjQ2LjAwMDAw
MDAwMCArMDEwMAorKysgZ2NjLTMuMy9nY2MvY29uZmlndXJlCTIwMDMtMDUtMTIgMTI6NDk6MDgu
MDAwMDAwMDAwICswMTAwCkBAIC03NDg1LDggKzc0ODUsOCBAQAogCSMgdGhlIGRhdGUgc3RyaW5n
IGFmdGVyIHRoZSB2ZXJzaW9uIG51bWJlci4KIAlsZF92ZXI9YCRnY2NfY3ZfbGQgLS12ZXJzaW9u
IDI+L2Rldi9udWxsIHwgaGVhZCAtMWAKIAlpZiBlY2hvICIkbGRfdmVyIiB8IGdyZXAgR05VID4g
L2Rldi9udWxsOyB0aGVuCi0JCWxkX3ZlcnM9YGVjaG8gJGxkX3ZlciB8IHNlZCAtbiAncyxeLipb
IAldXChbMC05XVswLTldKlwuWzAtOV1bMC05XSpcKFx8XC5bMC05XVswLTldKlwpXClcKFsgCV0u
Klx8XCkkLFwxLHAnYAotCQlsZF9kYXRlPWBlY2hvICRsZF92ZXIgfCBzZWQgLW4gJ3MsXi4qXChb
Mi05XVswLTldWzAtOV1bMC05XVwpWy1dKlwoWzAxXVswLTldXClbLV0qXChbMC0zXVswLTldXCku
KiQsXDFcMlwzLHAnYAorICAgICAgICAgICAgICAgIGxkX3ZlcnM9YGVjaG8gJGxkX3ZlciB8IHNl
ZCAtbiAncyxeLipbICBdXChbMC05XVswLTldKlwuWzAtOV1bMC05XSpcKFx8XC5bMC05XVswLTld
KlwoXHxcLlswLTldWzAtOV0qXClcKVwpXChbICBdLipcfFwpJCxcMSxwJ2AKKyAgICAgICAgICAg
ICAgICBsZF9kYXRlPWBlY2hvICRsZF92ZXIgfCBzZWQgLW4gJ3MsXi4qXChbMi05XVswLTldWzAt
OV1bMC05XVwpWy1dKlwoWzAxXVswLTldXClbLV0qXChbMC0zXVswLTldXCkuKiQsXDFcMlwzLHAn
YAogCQlpZiB0ZXN0IDAiJGxkX2RhdGUiIC1sdCAyMDAyMDQwNDsgdGhlbgogCQkJaWYgdGVzdCAt
biAiJGxkX2RhdGUiOyB0aGVuCiAJCQkJIyBJZiB0aGVyZSB3YXMgZGF0ZSBzdHJpbmcsIGJ1dCB3
YXMgZWFybGllciB0aGFuIDIwMDItMDQtMDQsIGZhaWwK
next reply other threads:[~2003-05-12 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 12:21 chris [this message]
2003-05-12 18:57 mmitchel
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=20030512121003.29703.qmail@sources.redhat.com \
--to=chris@stockwith.co.uk \
--cc=gcc-gnats@gcc.gnu.org \
--cc=mark@codesourcery.com \
/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).