From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] preparing rootfs with gcc in buildroot
Date: Thu, 21 Jun 2012 23:55:42 +0200 [thread overview]
Message-ID: <20120621235542.2e19e5be@skate> (raw)
In-Reply-To: <js03ef$2qm$1@dough.gmane.org>
Le Thu, 21 Jun 2012 21:24:31 +0000 (UTC),
Grant Edwards <grant.b.edwards@gmail.com> a ?crit :
> Right -- if you have buildroot build your compiler. If you're using
> an external compiler (e.g. one built separately with crosstool-ng),
> you need to tell it where buildroot's libraries and include files are.
No.
When you use an external toolchain in Buildroot, we generate a wrapper
that ensures that the external toolchain cross-compiler is always
properly called with the right argument.
Look at host/usr/bin/<arch>-linux-gcc, and you'll notice it's a symlink
to ext-toolchain-wrapper, which in turns calls the compiler. This
ext-toolchain-wrapper adds the --sysroot option.
So, regardless of whether you're using the internal toolchain backend,
the external toolchain backend, or the crosstool-ng toolchain backend,
you don't have to specify where the libraries and headers are. This was
done on purpose.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-06-21 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 12:16 [Buildroot] preparing rootfs with gcc in buildroot Kevin Wilson
2012-06-21 12:28 ` Thomas Petazzoni
2012-06-21 16:38 ` Kevin Wilson
2012-06-21 16:55 ` Grant Edwards
2012-06-21 20:31 ` Arnout Vandecappelle
2012-06-21 21:24 ` Grant Edwards
2012-06-21 21:55 ` 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=20120621235542.2e19e5be@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.