From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] external toolchain and sysroot
Date: Fri, 26 Mar 2010 01:04:33 +0000 (UTC) [thread overview]
Message-ID: <hoh171$jf0$1@dough.gmane.org> (raw)
In-Reply-To: 20100325233452.3794166b@surf
On 2010-03-25, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> On Thu, 25 Mar 2010 18:08:49 +0000 (UTC)
> Grant Edwards <grant.b.edwards@gmail.com> wrote:
>
>> Based on my sample of three packages (two had the problem), I'm
>> guessing it's a very common problem. It looks like the buildroot
>> developers use external toolchains that don't require a --sysroot
>> option.
>
> They do.
>
> What we do to support external toolchains is :
>
> * We copy the full sysroot of the toolchain into $(STAGING_DIR)
> * We copy just the C library and related libraries from the sysroot to
> the $(TARGET_DIR)
Agreed.
> * We pass --sysroot $(STAGING_DIR) to every gcc/ld invocation, so that
> gcc/ld find the libraries and header files correctly.
Perhaps that's what's supposed to happen, but there appear to be a lot
of packages where it doesn't happen (at least for some of us).
> Actually, this mechanism *only* works with toolchain supporting
> --sysroot. Toolchains *not* supporting --sysroot are rejected (see
> toolchain/external-toolchain/ext-tool.mk).
True.
--
Grant
next prev parent reply other threads:[~2010-03-26 1:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 15:28 [Buildroot] external toolchain and sysroot Yury Luneff
2010-03-25 16:14 ` Grant Edwards
2010-03-25 17:12 ` Yury Luneff
2010-03-25 17:16 ` Yury Luneff
2010-03-25 18:08 ` Grant Edwards
2010-03-25 22:34 ` Thomas Petazzoni
2010-03-26 1:04 ` Grant Edwards [this message]
2010-03-26 19:24 ` Thomas Petazzoni
2010-03-27 1:10 ` Grant Edwards
2010-03-27 8:22 ` Thomas Petazzoni
2010-03-27 15:05 ` Grant Edwards
2010-04-14 13:42 ` Grant Edwards
2010-03-25 22:32 ` Thomas Petazzoni
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='hoh171$jf0$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--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