[Buildroot] external toolchain and sysroot
Grant Edwards
grant.b.edwards at gmail.com
Fri Mar 26 01:04:33 UTC 2010
On 2010-03-25, Thomas Petazzoni <thomas.petazzoni at free-electrons.com> wrote:
> On Thu, 25 Mar 2010 18:08:49 +0000 (UTC)
> Grant Edwards <grant.b.edwards at 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
More information about the buildroot
mailing list