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] Various problem using buildroot-2012.05
Date: Mon, 18 Jun 2012 08:45:48 +0200	[thread overview]
Message-ID: <20120618084548.76c4bed8@skate> (raw)
In-Reply-To: <1339990515.26331.YahooMailClassic@web161404.mail.bf1.yahoo.com>

Le Sun, 17 Jun 2012 20:35:15 -0700 (PDT),
Ming-Ching Tiew <mctiew@yahoo.com> a ?crit :

> I encountered various problems using buildroot-2012.05, all to do
> with using buildroot as a chroot build environment.

Why would you do this?

Buildroot is here to cross-compile your libraries and applications, it
really doesn't make much sense to use it to generate a chrooted
environment in which you compile your applications. At least, that's
not how Buildroot developers/users typically use Buildroot, so it's an
area (using a native compiler on the target, with development files)
that doesn't receive a lot of attention, hence the problems you are
facing.

To the community: there seem to be an increasing number of people who
misunderstand how to use Buildroot properly. Should we simply get rid
of the "toolchain on target" option? Should we write a FAQ question
about this? Generally speaking, I don't think Buildroot is the good
tool to build a full-featured system that includes a compiler and all
related development tools to build stuff on the target. What do others
think about this?

Best regards,

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

  parent reply	other threads:[~2012-06-18  6:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18  3:35 [Buildroot] Various problem using buildroot-2012.05 Ming-Ching Tiew
2012-06-18  5:55 ` Ming-Ching Tiew
2012-06-18  6:45 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-18  7:46 Ming-Ching Tiew
2012-06-18  8:36 ` Thomas Petazzoni
2012-11-10 14:28   ` Bernd Kuhls
2012-11-10 14:51     ` Stefan Fröberg
2012-11-10 20:21       ` Bernd Kuhls
2012-11-11 22:47       ` Arnout Vandecappelle
2012-11-12  0:04         ` Stefan Fröberg
2012-11-12  7:36           ` 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=20120618084548.76c4bed8@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