From: Andreas Schwab <schwab@linux-m68k.org>
To: david.hagood@gmail.com
Cc: binutils@sourceware.org
Subject: Re: Weird error cross-compiling glibc with binutils 2.22 or head
Date: Fri, 03 Feb 2012 23:02:00 -0000 [thread overview]
Message-ID: <m2pqdvo70x.fsf@igel.home> (raw)
In-Reply-To: <34bc660d9f725c71ee7a72236bbdcd1f.squirrel@localhost> (david hagood's message of "Fri, 3 Feb 2012 16:51:04 -0600")
The line is coming literally from the Makerules file.
In any way, this has nothing to do with bintuils. You need to fix the
sed command not to put the erroneous line there.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-02-03 23:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 22:51 david.hagood
2012-02-03 23:02 ` Andreas Schwab [this message]
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=m2pqdvo70x.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=binutils@sourceware.org \
--cc=david.hagood@gmail.com \
/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).