From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 3049] New: binutils prior to 2.21 have a sysroot bug in ld
Date: Thu, 6 Jan 2011 07:07:25 +0000 (UTC) [thread overview]
Message-ID: <bug-3049-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=3049
Summary: binutils prior to 2.21 have a sysroot bug in ld
Product: buildroot
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: rick at sloservers.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 2839
--> https://bugs.busybox.net/attachment.cgi?id=2839
Patch I used to test with binutils-2.20.1
I ran into problems using buildroot to cross-compile mpc (and gcc-4.5.x for
which mpc is a dependency). The build would fail and the cross-compile-ld
would complain that it couldn't find /lib//libc.so.0
It turns out this is a bug in ld from binutils that was fixed in binutils 2.21:
https://bugs.launchpad.net/binutils/+bug/625320
Basically ld ignores the sysroot path when absolute library paths are given,
which causes errors when cross-compiling.
This issue affects any package that uses absolute library paths, such as mpc
and others.
The fix (which is basically this
http://bugs.gentoo.org/attachment.cgi?id=195936) ought to be added to the
buildroot patches for binutils versions prior to 2.21.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-01-06 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 7:07 bugzilla at busybox.net [this message]
2011-01-06 8:19 ` [Buildroot] [Bug 3049] binutils prior to 2.21 have a sysroot bug in ld bugzilla at busybox.net
2011-01-06 8:56 ` bugzilla at busybox.net
2011-01-06 18:48 ` bugzilla at busybox.net
2011-01-07 12:24 ` [Buildroot] [Bug 3049] binutils " bugzilla at busybox.net
2012-10-21 21:07 ` bugzilla at busybox.net
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=bug-3049-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.