Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] compiler plugins & compiling the kernel
Date: Sat, 20 Aug 2016 20:01:19 +0200	[thread overview]
Message-ID: <20160820200119.4ec5848b@free-electrons.com> (raw)
In-Reply-To: <CAK7rcp_m+9YC6gJ0xyarD217F4wyjwjg9QSdBLzVgPJ9QLrm7w@mail.gmail.com>

Hello,

On Sat, 20 Aug 2016 13:10:07 -0400, Kenneth Adam Miller wrote:

> I've noticed that when the kernel is built, it appears to always be
> built with the host compiler, and not the buildroot specified cross
> compiler. Why is that?

This is not true, the kernel is built with the cross-compiler.
Otherwise, Buildroot would never be able to build an ARM, PowerPC or
MIPS kernel on a x86 or x86-64 build machine.

> In addition, for some pax related options, it requires gcc plugins for
> the version being used. That means that I would have to have plugin
> support for my host, correct?

No, you would need support for plugins in the cross-compiler.

> I don't believe that there is a way to
> enable plugin support for the buildroot toolchain or for crosstool. At
> least, when I looked and searched I didn't see any option that
> mentioned that. I just want to make sure that I have it correct in
> that my host compiler is being used to build the kernel.

You're not correct. Support for plugins should be added to the
cross-compiler if you need plugin support to build your kernel.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-08-20 18:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20 17:10 [Buildroot] compiler plugins & compiling the kernel Kenneth Adam Miller
2016-08-20 18:01 ` Thomas Petazzoni [this message]
2016-08-20 22:39   ` Kenneth Adam Miller
2016-08-21  3:43     ` Kenneth Adam Miller
2016-08-24  0:46       ` Arnout Vandecappelle
2016-08-24  0:49         ` Kenneth Adam Miller
2016-08-24  9:34         ` Peter Korsgaard
2016-08-25  5:15           ` Kenneth Adam Miller
     [not found] ` <CAMKF1sr1ZvZZW++J4pxixtr1KXGi8qGBRFEJGoaJSc_=Yn=x3Q@mail.gmail.com>
     [not found]   ` <CAMKF1sqteu5nK9NGfr1M=A3nZFk2H_J5zhu3BYq0110sjz8vDQ@mail.gmail.com>
2016-08-21  3:55     ` Khem Raj
2016-08-21 15:21       ` Kenneth Adam Miller

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=20160820200119.4ec5848b@free-electrons.com \
    --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