From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Why is sysroot under i686-buildroot-linux-gnu?
Date: Wed, 8 Jan 2014 06:04:25 +0800 [thread overview]
Message-ID: <20140108060425.59c340ca@skate> (raw)
In-Reply-To: <CAJpxd048a0Yw7HhO3kh5Sc7opQPiOncNzUhgSLR3JuEXgvOiuQ@mail.gmail.com>
Dear Bryce Schober,
On Tue, 7 Jan 2014 12:43:41 -0800, Bryce Schober wrote:
> On Mon, Jan 6, 2014 at 10:45 PM, Thomas Petazzoni <
> thomas.petazzoni at free-electrons.com> wrote:
>
> > Ok, I think I see what you mean. Can you test the following patch and
> > see if it fixes the problem for you?
>
> I don't see how it could, at least not as I was thinking, since
> STAGING_SUBDIR still uses $(GNU_TARGET_NAME)...
Yes, but the name of the compiler in host/usr/bin now matches the
sysroot directory name, which is what you requested in the first place:
$ ls output/host/usr/
arm-buildroot-linux-uclibcgnueabi bin lib share
$ ls output/host/usr/bin/arm-buildroot-linux-uclibcgnueabi-gcc
output/host/usr/bin/arm-buildroot-linux-uclibcgnueabi-gcc
Note that we are *not* interested in having the sysroot directory name
match the tuple of your original toolchain. What this patch is doing is
that it is making sure that the sysroot directory name matches the
tuple of the Buildroot generated toolchain (which is either a toolchain
fully built by Buildroot, or a set of symlinks+wrapper when an external
toolchain is used).
So the fact that the compiler in output/host/opt/ext-toolchain/ might
have a different tuple is expected.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-01-07 22:04 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
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 [this message]
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=20140108060425.59c340ca@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