From: Jean-Mickael Guerin <jean-mickael.guerin@6wind.com>
To: buildroot@busybox.net
Subject: [Buildroot] external toolchains and sysroot
Date: Tue, 23 Oct 2012 08:45:30 +0200 [thread overview]
Message-ID: <50863D0A.40809@6wind.com> (raw)
In-Reply-To: <20121021114154.3d23d89b@skate>
On 21/10/2012 11:41, Thomas Petazzoni wrote:
> I am the one who wrote the external toolchain support as it is now.
> Initially, things were working as you suggested, i.e keep the sysroot
> in its original place, and use -I/-L to point to the headers and
> libraries that Buildroot adds. It/mostly/ works, but causes for some
> packages horrible problems with libtool.
>
> I don't have the time right now to dig into the archives, but this is a
> problem we worked on around December 2008, and it has allowed the
> external toolchain support to work nicely and properly since then.
>
> If you have problems with external toolchain support, don't hesitate to
> point me to the toolchain you're using, and how to reproduce your
> problem. I am fairly sure it is not related to the fact that we're
> copying the sysroot.
Well, the issue *is* this large copy.
We can improve the share of toolchains among multiple builds, and
simplify this code for ext toolchain support (btw there is hack to avoid
too big usr/locale..).
I can propose the patch, but which are the options to get confident?
Do we have ext-toolchain in the serie of daily auto-build?
I could find in archive some discussion about Qtopia, DirectFB, but
nothing explicitly related to sysroot or library path.
Someone else may remember other problem? a specific toolchain?
Regards,
Jean-Mickael
next prev parent reply other threads:[~2012-10-23 6:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 9:10 [Buildroot] external toolchains and sysroot Jean-Mickael Guerin
2012-10-19 9:38 ` Richard Braun
2012-10-19 9:46 ` Jean-Mickael Guerin
2012-10-19 9:57 ` Richard Braun
2012-10-19 10:02 ` Richard Braun
2012-10-19 11:06 ` Jean-Mickael Guerin
2012-10-19 11:26 ` Richard Braun
2012-10-21 9:41 ` Thomas Petazzoni
2012-10-23 6:45 ` Jean-Mickael Guerin [this message]
2012-10-23 7:28 ` Thomas Petazzoni
2012-10-23 8:46 ` Arnout Vandecappelle
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=50863D0A.40809@6wind.com \
--to=jean-mickael.guerin@6wind.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.