All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain doesn't support --sysroot.
Date: Fri, 6 Aug 2010 20:00:30 +0200	[thread overview]
Message-ID: <20100806200030.0f798014@surf> (raw)
In-Reply-To: <201008061844.48326.yann.morin.1998@anciens.enib.fr>

Hello,

On Fri, 6 Aug 2010 18:44:48 +0200
"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> wrote:

> AFAIK, sysroot support in the toolchain is mandatory for use as an
> external toolchain in buildroot.

Correct.

We have an enhancement request, at
https://bugs.busybox.net/show_bug.cgi?id=1315, to extend Buildroot to
support non sysroot toolchains.

However, when I initially updated the support for external toolchains,
I tried *not* to use the sysroot capability, and in turned out to be a
nightmare. You could fairly easily get a basic build to work, but as
soon as you started adding slightly more complicated packages, it was
failing with strange issues. Using the --sysroot capability of the
toolchain turned out to be the most reasonable solution, and with gcc
supporting --sysroot since the beginning of the 4.x era, restricting
ourselves to sysrooted toolchains only didn't sound terribly
unreasonable.

Of course, if you want non-sysroot toolchains to work, feel free to
work on such a patch, and check that it indeed works to build a large
set of Buildroot packages. Bug #1315 mentionned above has such a patch,
but I'm not sure how well all the Buildroot packages behave with such a
patch applied. Don't hesitate to report your tries, successes and
failures.

Regards!

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

      reply	other threads:[~2010-08-06 18:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06 16:09 [Buildroot] External toolchain doesn't support --sysroot anthony henderson
2010-08-06 16:44 ` Yann E. MORIN
2010-08-06 18:00   ` 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=20100806200030.0f798014@surf \
    --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.