From: david.hagood@gmail.com
To: "Andreas Schwab" <schwab@linux-m68k.org>
Cc: binutils@sourceware.org
Subject: Re: Weird error cross-compiling glibc with binutils 2.22 or head
Date: Fri, 03 Feb 2012 22:51:00 -0000 [thread overview]
Message-ID: <34bc660d9f725c71ee7a72236bbdcd1f.squirrel@localhost> (raw)
You might actually READ my posting:
"
I have no idea where that is coming from: it's not in any of the makefiles
for binutils, glibc, or gcc, it's not in my host toolchain - and it
doesn't happen on PPC."
As in, no make file, no tool, nothing contains that line. So why Make is
putting it into the runtime is not clear. Yes, I can SEE that the command
line to sed contains that line - but WHY it contains that is not clear, as
it does not appear in the make file, nor in any of the tools.
next reply other threads:[~2012-02-03 22:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 22:51 david.hagood [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2012-02-06 14:54 david.hagood
2012-02-07 11:26 ` Alan Modra
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=34bc660d9f725c71ee7a72236bbdcd1f.squirrel@localhost \
--to=david.hagood@gmail.com \
--cc=binutils@sourceware.org \
--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).