From: Uri Moszkowicz <uri@4refs.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Trouble building AR
Date: Fri, 21 Jun 2013 19:19:00 -0000 [thread overview]
Message-ID: <CAMJd5ARBOjHxt7j03+CGGrJnUNXNJ-8oOD_2v8dfzG+oj=1mMw@mail.gmail.com> (raw)
In-Reply-To: <CAKOQZ8w7E1S+7z1XxU=xo-8QG-B0cY2kQMJKKTbKTyk-WgMJxA@mail.gmail.com>
Thanks for identifying it - good so I'm not crazy :) I tried your fix
and I think it worked? I get this error when linking now:
<.a file>: could not read symbols: Bad value
collect2: error: ld returned 1 exit status
I tried building the latest stable GCC, 4.8.1, and binutils, 2.23.2,
but an error buildling it too:
/lib64/ld-linux-x86-64.so.2: could not read symbols: Invalid operation
This is on a RHEL4u8WS machine.
On Wed, Jun 19, 2013 at 6:06 PM, Ian Lance Taylor <iant@google.com> wrote:
> On Wed, Jun 19, 2013 at 3:04 PM, Uri Moszkowicz <uri@4refs.com> wrote:
>> Log uploaded here:
>>
>> http://www.4refs.com/gcc.log
>>
>> It seems to be looking in the right places just not for the right
>> file. It looks for "real-ld", "collect-ld", and "ld-new" but not "ld".
>
> This looks like a bug. It looks like it has been fixed in current
> mainline. It looks like when you build with the binutils as a sibling
> directory, it finds ld-new in the ld directory. Then it mistakenly
> starts looking for that, rather than ld. I haven't tried but you may
> be able to work around this by using the GCC configure option
> --with-plugin-ld=/path/to/your/ld.
>
> Ian
prev parent reply other threads:[~2013-06-21 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 20:08 Uri Moszkowicz
2013-06-18 23:16 ` Ian Lance Taylor
2013-06-19 19:10 ` Uri Moszkowicz
2013-06-19 19:25 ` Ian Lance Taylor
2013-06-19 21:21 ` Uri Moszkowicz
2013-06-19 21:38 ` Ian Lance Taylor
2013-06-19 22:04 ` Uri Moszkowicz
2013-06-19 23:06 ` Ian Lance Taylor
2013-06-21 19:19 ` Uri Moszkowicz [this message]
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='CAMJd5ARBOjHxt7j03+CGGrJnUNXNJ-8oOD_2v8dfzG+oj=1mMw@mail.gmail.com' \
--to=uri@4refs.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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).