From: David Hagood <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: Sat, 04 Feb 2012 12:09:00 -0000 [thread overview]
Message-ID: <1328357349.2972.20.camel@chumley> (raw)
In-Reply-To: <m2mx8z2fkw.fsf@linux-m68k.org>
On Sat, 2012-02-04 at 09:00 +0100, Andreas Schwab wrote:
> That's exactly what you have to find out. It is absolutely obvious that
> this has nothing to do with binutils, because the erroneous line was
> explicitly written into linker script.
Except you seem to have missed the bit in my first post that this only
started happening AFTER I replaced the older version of binutils I was
cross-compiling with the newer version of binutils - that is, when I
stopped building binutils-2.20 for the cross environment and started
building binutils-2.22 for the cross environment. Now, I know that "post
hoc, ergo propter hoc" is a fallacy, but to start checking the
assumption that the thing I changed might have something to do with the
change is not unreasonable.
Look: if you don't want to help me, fine. Stop replying to my mails. But
I am seeing this. I am not the only one seeing this. I am pursuing this
on both the binutils board (because changing binutils seems to be what
precipitated the change) and on the libc board.
next prev parent reply other threads:[~2012-02-04 12:09 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
2012-02-03 23:53 ` David Hagood
2012-02-04 8:00 ` Andreas Schwab
2012-02-04 12:09 ` David Hagood [this message]
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=1328357349.2972.20.camel@chumley \
--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).