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] External toolchain improvements
Date: Thu, 2 Jul 2009 14:50:11 +0200	[thread overview]
Message-ID: <20090702145011.6b9f3fe9@surf> (raw)
In-Reply-To: <1246484614.21132.36.camel@coalu.atr>

Hi,

Le Wed, 01 Jul 2009 23:43:34 +0200,
Lionel Landwerlin <lionel.landwerlin@openwide.fr> a ?crit :

> Ok, I had another look at the ext-tool.mk makefile, and the sysroot
> dir is not copied because of the locale...
> 
> This current command to get the sysroot dir is :
> 
> SYSROOT_DIR=`$(TARGET_CC) -v 2>&1 | grep ^Configured | tr " " "\n" |
> grep -- "--with-sysroot" | cut -f2 -d=`;
> 
> which call (in my case) sh4-linux-gcc using the default locale and as
> my email address could suggest, my current locale is fr_FR.UTF-8. So
> grep ^Configured just fails.
> 
> Please apply the attached patch to your external-toolchain branch.

Ok, thanks for patch. I should probably add a little bit of error
checking in this external toolchain thing.

> >  * Buildroot version
> 
> Your external-toolchain branch

Which doesn't exist anymore since it has been merged in the official
Buildroot :-)

But ok, fine, I know what you're using.

> >  * Error messages
> 
> I will try to retry with the fix on the locale first.

For sure if Buildroot didn't properly copy the sysroot to the staging
dir, the rest of the compilation could not work.

That said, your configuration file enables a relatively large set of
packages that I haven't tested with the external toolchain
configuration. Most if not all of the packages using the
Makefile.autotools.in machinery should build flawlessly, but the
packages using their own stuff in the .mk might break. Don't hesitate
to report the breakage with the associated error messages (or the full
build output), it's usually relatively easy to fix.

Thanks!

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

  reply	other threads:[~2009-07-02 12:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1246405094.1110.buildroot@busybox.net>
2009-06-30 23:50 ` [Buildroot] External toolchain improvements Lionel Landwerlin
2009-06-30 23:54 ` Lionel Landwerlin
2009-07-01 14:05   ` Thomas Petazzoni
2009-07-01 21:43     ` Lionel Landwerlin
2009-07-02 12:50       ` Thomas Petazzoni [this message]
2009-07-03  6:01         ` Lionel Landwerlin
2009-07-03  8:13           ` Thomas Petazzoni
2009-07-03 21:24             ` Lionel Landwerlin
2009-07-06  0:51             ` Lionel Landwerlin
2009-07-13 19:26         ` Lionel Landwerlin
2009-07-14 14:41           ` Thomas Petazzoni
2009-07-14 19:51             ` Lionel Landwerlin
2009-06-01 16:54 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=20090702145011.6b9f3fe9@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox