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] preparing rootfs with gcc in buildroot
Date: Thu, 21 Jun 2012 14:28:48 +0200	[thread overview]
Message-ID: <20120621142848.4caafde0@skate> (raw)
In-Reply-To: <CAGXs5wVgC+e_BUAOPgvL-vGqo4pusF3iTLFz_7Fb_Jfvrvv+Hg@mail.gmail.com>

Le Thu, 21 Jun 2012 15:16:14 +0300,
Kevin Wilson <wkevils@gmail.com> a ?crit :

> I run:
> make menuconfig
>   Package selection for target
>      Development tools
>         "gcc needs development files in target filesystems"

Yes, you have to enable BR2_HAVE_DEVFILES (in Build options).

However, beware that the usage of the native toolchain on the target is
rarely used and tested by Buildroot developers. Buildroot is here to
cross-compile all your applications and libraries, so it generally
doesn't make much sense to have a native toolchain on the target, so we
don't pay too much attention to this.

What would you like to build on your target? Why don't you
cross-compile it?

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-06-21 12:28 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 [this message]
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

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=20120621142848.4caafde0@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