From: Alan Modra <amodra@gmail.com>
To: david.hagood@gmail.com
Cc: Andreas Schwab <schwab@linux-m68k.org>,
jreiser@bitwagon.com, binutils@sourceware.org
Subject: Re: Weird error cross-compiling glibc with binutils 2.22 or head
Date: Tue, 07 Feb 2012 11:26:00 -0000 [thread overview]
Message-ID: <20120207112546.GL22267@bubble.grove.modra.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2012-02-07 11:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 14:54 david.hagood
2012-02-07 11:26 ` Alan Modra [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-03 22:51 david.hagood
2012-02-03 23:02 ` Andreas Schwab
2012-02-03 23:53 ` David Hagood
2012-02-04 8:00 ` Andreas Schwab
2012-02-04 12:09 ` David Hagood
2012-02-04 14:40 ` Andreas Schwab
2012-02-03 22:00 david.hagood
2012-02-03 22:41 ` Andreas Schwab
2012-02-04 1:30 ` John Reiser
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=20120207112546.GL22267@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=david.hagood@gmail.com \
--cc=jreiser@bitwagon.com \
--cc=schwab@linux-m68k.org \
/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).