This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

other/9479: ld --version parsing in gcc configury fails on latest FSF binutils-2.13.2.1


>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:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]