From: Michael Hope <michael.hope@linaro.org>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: crossgcc@sourceware.org
Subject: Re: crosstool-ng: binutils 2.21.53 affected by #13195
Date: Tue, 03 Jan 2012 20:24:00 -0000 [thread overview]
Message-ID: <CANLjY-mLvu3tbEtbgsV1jDp8+T4qJ_cuASN8LRESyu0icKPnCw@mail.gmail.com> (raw)
In-Reply-To: <20120101154947.63302eea@skate>
On Mon, Jan 2, 2012 at 3:49 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> Building a x86_64 eglibc toolchain with crosstool-ng, I'm affected by
> the following link problem:
>
> /home/test/toolchains/ctng-x86_64-unknown-linux-gnu/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.6.1/../../../../x86_64-unknown-linux-gnu/bin/ld.bfd: busybox_unstripped: local symbol `_dl_argv@@GLIBC_PRIVATE' in /home/test/outputs/test-1063/host/usr/x86_64-unknown-linux-gnu/sysroot/lib64/ld-linux-x86-64.so.2 is referenced by DSO
> /home/test/toolchains/ctng-x86_64-unknown-linux-gnu/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.6.1/../../../../x86_64-unknown-linux-gnu/bin/ld.bfd: final link failed: Bad value
>
> which is exactly
>
> http://sourceware.org/bugzilla/show_bug.cgi?id=13232
>
> which itself has been marked as a duplicate of
>
> http://sourceware.org/bugzilla/show_bug.cgi?id=13195
>
> The latter has been fixed in binutils HEAD (2.23) and in the 2.22 branch.
Hi Thomas. I see the fix made it into the 2.22 release which is
supported by crosstool-NG tip. Can you use tip, or are you asking for
the 2.22 support to be backported to the current release?
-- Michael
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2012-01-03 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-01 14:50 Thomas Petazzoni
2012-01-03 20:24 ` Michael Hope [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=CANLjY-mLvu3tbEtbgsV1jDp8+T4qJ_cuASN8LRESyu0icKPnCw@mail.gmail.com \
--to=michael.hope@linaro.org \
--cc=crossgcc@sourceware.org \
--cc=thomas.petazzoni@free-electrons.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).