From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Why is sysroot under i686-buildroot-linux-gnu?
Date: Sat, 4 Jan 2014 22:28:32 +0100 [thread overview]
Message-ID: <20140104222832.7a8dab5b@skate> (raw)
In-Reply-To: <CAJpxd07vs10v6uhOe3=_a=Rj-40x+Q8yWh0cK+YbTnP1HdzLTw@mail.gmail.com>
Dear Bryce Schober,
On Fri, 3 Jan 2014 15:54:09 -0800, Bryce Schober wrote:
> I'm using a custom external toolchain built by crosstool-ng that's a
> fairly ordinary configuration, other than using an old gcc-4.3 and
> glibc-2.9, ending up with a i686-unknown-linux-gnu toolchain.
>
> Why does buildroot end up installing the toolchain sysroot under
> output/host/usr/i686-buildroot-linux-gnu instead of under
> output/host/usr/i686-unknown-linux-gnu?
Just because we set the vendor part of the tuple to "Buildroot" to
distinguish the Buildroot compiler/sysroot from the one of the original
toolchain. There is no strong need for this, it's just a bit nicer.
> This is causing some problems in some of my external makefiles I have
> that expect the sysroot dir to match the toolchain tuple...
They do: in host/usr/bin/, you have a compiler whose tuple matches the
sysroot directory name.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-04 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 23:54 [Buildroot] Why is sysroot under i686-buildroot-linux-gnu? Bryce Schober
2014-01-04 21:28 ` Thomas Petazzoni [this message]
2014-01-06 18:39 ` Bryce Schober
2014-01-07 6:45 ` Thomas Petazzoni
2014-01-07 20:43 ` Bryce Schober
2014-01-07 22:04 ` 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=20140104222832.7a8dab5b@skate \
--to=thomas.petazzoni@free-electrons.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