From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 699] New: Buildroot fails to copy libstdc++ to target when using external toolchain
Date: Mon, 9 Nov 2009 23:37:11 +0000 (UTC) [thread overview]
Message-ID: <bug-699-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=699
Host: x86
Target: arm926t
Summary: Buildroot fails to copy libstdc++ to target when using
external toolchain
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: maksim.rayskiy at conexant.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
When buildroot builds arm-linux-uclibcgnueabi toolchain, some libraries get
installed into <sysroot>/lib, others - including libstdc++ - into
<sysroot>/usr/arm-linux-uclibcgnueabi/lib.
If I use such a toolchain as an external toolchain for another buildroot build,
buildroot does not find libraries in <sysroot>/usr/arm-linux-uclibcgnueabi/lib.
Previous versions of buildroot used -print-file-name option of gcc to locate a
library. Current version only checks in <sysroot>/lib folder.
--
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:[~2009-11-09 23:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 23:37 bugzilla at busybox.net [this message]
2010-02-21 18:13 ` [Buildroot] [Bug 699] Buildroot fails to copy libstdc++ to target when using external toolchain bugzilla at busybox.net
2010-02-21 18:51 ` bugzilla at busybox.net
2010-02-21 19:02 ` bugzilla at busybox.net
2010-04-09 14:54 ` bugzilla at busybox.net
2010-05-21 23:03 ` 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-699-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.