From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1315] New: Allow use of older external toolchains without sysroot support
Date: Tue, 16 Mar 2010 00:36:31 +0000 (UTC) [thread overview]
Message-ID: <bug-1315-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=1315
Summary: Allow use of older external toolchains without sysroot
support
Product: buildroot
Version: 2010.02
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: cls at seawood.org
CC: buildroot at uclibc.org
Estimated Hours: 0.0
I'm using buildroot to create packages that are binary compatible with the
default rootfs provides in my Patriot Corza NAS. As such, I'm unable to
upgrade to a newer toolchain that supports --sysroot.
The attached patch updates package/Makefile.in, ext-tool.mk and various package
.mks to allow buildroot to be built with an external toolchain that does not
use --sysroot (gcc-3.4.6, in my case). The use of --sysroot is now controlled
by the BR2_TOOLCHAIN_EXTERNAL_SYSROOT option.
Most of the other changes just involve passing TARGET_CONFIGURE_ENV to the
configure or make calls for each package.
There's also a change to override the broken getline detection in sed when
using an external glibc toolchain.
--
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:[~2010-03-16 0:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 0:36 bugzilla at busybox.net [this message]
2010-03-16 4:39 ` [Buildroot] [Bug 1315] Allow use of older external toolchains without sysroot support bugzilla at busybox.net
2010-03-16 7:42 ` bugzilla at busybox.net
2010-03-16 18:05 ` bugzilla at busybox.net
2010-04-09 14:54 ` bugzilla at busybox.net
2010-07-23 7:06 ` bugzilla at busybox.net
2012-07-20 8:22 ` 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-1315-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox