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

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

[Greg Schafer]

The following reply was made to PR other/9479; it has been noted by GNATS.

From: Greg Schafer <gschafer@zip.com.au>
To: gcc-gnats@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: other/9479: ld --version parsing in gcc configury fails on latest FSF binutils-2.13.2.1
Date: Tue, 1 Apr 2003 15:21:44 +1000

 As mentioned in this post:-
 
 http://gcc.gnu.org/ml/gcc/2003-02/msg00329.html
 
 the 2nd set of patches are incorrect and should not be applied.
 
 
 However, the original patch IS correct and was applied to 3.2.2 but is still
 not applied to the 3.3 and 3.4 branches.
 
 
 Here is where Jakub reviewed the original patch:-
 
 http://gcc.gnu.org/ml/gcc-bugs/2003-01/msg01712.html
 
 
 And here is where it got applied:-
 
 http://gcc.gnu.org/ml/gcc-cvs/2003-02/msg00143.html
 
 
 This needs to be applied to gcc-3.3 before release!
 
 Greg

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

[Greg Schafer]

The following reply was made to PR other/9479; it has been noted by GNATS.

From: Greg Schafer <gschafer@zip.com.au>
To: gcc-gnats@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: other/9479: ld --version parsing in gcc configury fails on latest FSF binutils-2.13.2.1
Date: Fri, 7 Feb 2003 13:24:38 +1100

 On Fri, Feb 07, 2003 at 01:14:55PM +1100, Greg Schafer wrote:
 > As of this writing, the current FSF binutils release is still 2.23.2.1 so
 > people using that version with gcc-3.3 & 3.4 are building subtley broken
 > gcc's.
 
 Of course, I meant, "is still 2.13.2.1".
 
 Greg

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

[Greg Schafer]

The following reply was made to PR other/9479; it has been noted by GNATS.

From: Greg Schafer <gschafer@zip.com.au>
To: gcc-gnats@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: other/9479: ld --version parsing in gcc configury fails on latest FSF binutils-2.13.2.1
Date: Fri, 7 Feb 2003 13:14:55 +1100

 --gBBFr7Ir9EOA20Yy
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 
 Here is a better patch that also allows for binutils version strings with 5
 or more digits (a la HJL binutils releases).
 
 The initial patch WAS applied to the gcc-3.2 branch before the release of
 gcc-3.2.2 so the immediate problem was fixed.
 
 However, this new patch should fix the problem for ever more and therefore
 should be applied to all branches (3.2, 3.3 & 3.4).
 
 As of this writing, the current FSF binutils release is still 2.23.2.1 so
 people using that version with gcc-3.3 & 3.4 are building subtley broken
 gcc's.
 
 There are 2 patches below. The 1st will apply to 3.4 & 3.3. The second will
 apply to 3.2
 
 Patch this time supplied by:-
 Dan Osterrath <do3@mail.inf.tu-dresden.de>
 
 I have tested it by throwing various strings at the regex and it does the
 right thing in all cases.
 
 
 Greg
 
 --gBBFr7Ir9EOA20Yy
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename="gcc.patch.new.3.4"
 
 diff -uNr gcc.orig/gcc/configure.in gcc/gcc/configure.in
 --- gcc.orig/gcc/configure.in	2003-02-07 12:49:24.000000000 +1100
 +++ gcc/gcc/configure.in	2003-02-07 12:53:34.000000000 +1100
 @@ -1675,7 +1675,7 @@
  	ld_ver=`$gcc_cv_ld --version 2>/dev/null | head -1`
  	if echo "$ld_ver" | grep GNU > /dev/null; then
  changequote(,)dnl
 -		ld_vers=`echo $ld_ver | sed -n 's,^.*[ 	]\([0-9][0-9]*\.[0-9][0-9]*\(\|\.[0-9][0-9]*\)\)\([ 	].*\|\)$,\1,p'`
 +		ld_vers=`echo $ld_ver | sed -n 's,^.*[  ]\([0-9][0-9]*\.[0-9][0-9]*\(\|\.[0-9][0-9]*\)*\)\([     ].*\|\)$,\1,p'`
  		ld_date=`echo $ld_ver | sed -n 's,^.*\([2-9][0-9][0-9][0-9]\)[-]*\([01][0-9]\)[-]*\([0-3][0-9]\).*$,\1\2\3,p'`
  		if test 0"$ld_date" -lt 20020404; then
  			if test -n "$ld_date"; then
 
 --gBBFr7Ir9EOA20Yy
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename="gcc.patch.new.3.2"
 
 diff -uNr gcc.orig/gcc/configure.in gcc/gcc/configure.in
 --- gcc.orig/gcc/configure.in	2003-02-05 13:44:33.000000000 +1100
 +++ gcc/gcc/configure.in	2003-02-07 13:11:02.000000000 +1100
 @@ -1537,7 +1537,7 @@
  	ld_ver=`$gcc_cv_ld --version 2>/dev/null | head -1`
  	if echo "$ld_ver" | grep GNU > /dev/null; then
  changequote(,)dnl
 -		ld_vers=`echo $ld_ver | sed -n 's,^.*[ 	]\([0-9][0-9]*\.[0-9][0-9]*\(\|\.[0-9][0-9]*\(\|\.[0-9][0-9]*\)\)\)\([ 	].*\|\)$,\1,p'`
 +		ld_vers=`echo $ld_ver | sed -n 's,^.*[  ]\([0-9][0-9]*\.[0-9][0-9]*\(\|\.[0-9][0-9]*\)*\)\([     ].*\|\)$,\1,p'`
  		ld_date=`echo $ld_ver | sed -n 's,^.*\([2-9][0-9][0-9][0-9]\)[-]*\([01][0-9]\)[-]*\([0-3][0-9]\).*$,\1\2\3,p'`
  		if test 0"$ld_date" -lt 20020404; then
  			if test -n "$ld_date"; then
 
 --gBBFr7Ir9EOA20Yy--

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

[Greg Schafer]

The following reply was made to PR other/9479; it has been noted by GNATS.

From: Greg Schafer <gschafer@zip.com.au>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, jakub@redhat.com, drow@mvista.com
Cc:  
Subject: Re: other/9479: ld --version parsing in gcc configury fails on latest FSF binutils-2.13.2.1
Date: Wed, 29 Jan 2003 02:19:32 +1100

 --/9DWx/yDrRhgMJTb
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 
 Ok, here's a patch that seems to work.
 
 Could somebody pls verify and check in if ok?
 
 Patch provided by:-
 
 Chris Lingard <chris@stockwith.co.uk> and
 Dan Osterrath <do3@mail.inf.tu-dresden.de>
 
 Greg
 
 --/9DWx/yDrRhgMJTb
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename="gcc-fix.patch"
 
 diff -uNr gcc.orig/configure.in gcc/configure.in
 --- gcc.orig/configure.in	2003-01-28 19:11:33.000000000 +1100
 +++ gcc/configure.in	2003-01-29 01:53:38.000000000 +1100
 @@ -1674,7 +1674,7 @@
  	ld_ver=`$gcc_cv_ld --version 2>/dev/null | head -1`
  	if echo "$ld_ver" | grep GNU > /dev/null; then
  changequote(,)dnl
 -		ld_vers=`echo $ld_ver | sed -n 's,^.*[ 	]\([0-9][0-9]*\.[0-9][0-9]*\(\|\.[0-9][0-9]*\)\)\([ 	].*\|\)$,\1,p'`
 +		ld_vers=`echo $ld_ver | sed -n 's,^.*[  ]\([0-9][0-9]*\.[0-9][0-9]*\(\|\.[0-9][0-9]*\(\|\.[0-9][0-9]*\)\)\)\([     ].*\|\)$,\1,p'`
  		ld_date=`echo $ld_ver | sed -n 's,^.*\([2-9][0-9][0-9][0-9]\)[-]*\([01][0-9]\)[-]*\([0-3][0-9]\).*$,\1\2\3,p'`
  		if test 0"$ld_date" -lt 20020404; then
  			if test -n "$ld_date"; then
 
 --/9DWx/yDrRhgMJTb--

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

[gschafer]

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