public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: gschafer@zip.com.au To: gcc-gnats@gcc.gnu.org Cc: jakub@redhat.com, drow@mvista.com Subject: other/9479: ld --version parsing in gcc configury fails on latest FSF binutils-2.13.2.1 Date: Tue, 28 Jan 2003 14:36:00 -0000 [thread overview] Message-ID: <20030128143101.1458.qmail@sources.redhat.com> (raw) >Number: 9479 >Category: other >Synopsis: ld --version parsing in gcc configury fails on latest FSF binutils-2.13.2.1 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Jan 28 14:36:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Greg Schafer >Release: all recent gcc's - 3.2, 3.3 & 3.4 >Organization: >Environment: i686-pc-linux-gnu >Description: gcc's configure script attempts to determine the "ld" version string in one of it's tests but fails to do so when used with the latest FSF release of binutils (2.13.2.1). The configury works fine when used with version 2.13.2 so it appears the extra digit on the current release is confusing the regexp. The regexp needs to be reworked but I haven't been able to come up with a working version up to this point. This is a critical problem as it results in gcc not correctly identifying that our binutils has .hidden support which then results in non-functioning __cxa_atexit support in glibc which is obviously bad when gcc is now always configured with --enable__cxa_atexit. Ultimate result is segfaulting c++ binaries. More info can be found here:- http://gcc.gnu.org/ml/gcc/2003-01/msg01396.html >How-To-Repeat: Install FSF binutils-2.13.2.1 then configure gcc to use those binutils and watch as it says:- checking assembler hidden support... no >Fix: Fix the regexp in the configure script. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-01-28 14:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-28 14:36 gschafer [this message] 2003-01-28 15:26 Greg Schafer 2003-02-07 2:16 Greg Schafer 2003-02-07 2:26 Greg Schafer 2003-04-01 5:26 Greg Schafer
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=20030128143101.1458.qmail@sources.redhat.com \ --to=gschafer@zip.com.au \ --cc=drow@mvista.com \ --cc=gcc-gnats@gcc.gnu.org \ --cc=jakub@redhat.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: 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).