This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: Weird error cross-compiling glibc with binutils 2.22 or head
- From: Alan Modra <amodra at gmail dot com>
- To: david dot hagood at gmail dot com
- Cc: Andreas Schwab <schwab at linux-m68k dot org>, jreiser at bitwagon dot com, binutils at sourceware dot org
- Date: Tue, 7 Feb 2012 21:55:46 +1030
- Subject: Re: Weird error cross-compiling glibc with binutils 2.22 or head
- References: <e902f1816a9708832691f5c476db0811.squirrel@localhost>
On Mon, Feb 06, 2012 at 08:54:20AM -0600, david.hagood@gmail.com wrote:
> Since that variable is binutils, I am on this list.
Andreas kindly pointed you at the glibc Makerules file. If you had
looked instead of whining you would have found a couple of lines in
that file:
PROVIDE(__start___libc_subfreeres = .);\
__libc_subfreeres : { *(__libc_subfreeres) }\
which more or less match your make output:
PROVIDE(__start__es : {subfreeres = .);\
__libc_subfreeres : { *(__libc_subfreeres) }\
Except somehow the string "_libc_" on the first line has been replaced
by "es : {". That's hardly likely to be due to a binutils gremlin.
As to why your toolchain builds with binutils-2.20 but not with
binutils-2.22, it is likely some glibc configure test detecting ld
features, enabling different make rules or parts thereof. There's one
right in the rule I partially quote above.
--
Alan Modra
Australia Development Lab, IBM