From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/8] external toolchain: use LANG=C when calling gcc -v
Date: Fri, 17 Jul 2009 22:50:35 +0200 [thread overview]
Message-ID: <87ocrjhw4k.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <fd5570970e1a488815b8ca94b516f92901cefacb.1247819731.git.thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Fri\, 17 Jul 2009 10\:35\:30 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Lionel Landwerlin <lionel.landwerlin@openwide.fr> reported that using
Thomas> the external toolchain support when LANG=fr_FR.UTF-8 doesn't work,
Thomas> since the messages printed by gcc -v are translated in another
Thomas> language, defeating the grep ^Configured test.
Thomas> Therefore, as per Lionel suggestion, we force LANG=C when calling
Thomas> $(TARGET_CC) -v.
I use LANG=C/en_US myself, but wouldn't it make sense to fix this
globally in the main Makefile instead as we might have similar
problems other places? The only disadvantage I can think of is that
the users will get error messages in English (but that's a good thing
when they send logs to us).
Could someone with a different locale test that please? E.G. add an:
export LANG=C
To the toplevel Makefile.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-07-17 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 8:35 [Buildroot] [pull request] Pull request for branch external-toolchain Thomas Petazzoni
2009-07-17 8:35 ` [Buildroot] [PATCH 1/8] external toolchain: fix libraries copy and add ARM ABI check Thomas Petazzoni
2009-07-17 8:35 ` [Buildroot] [PATCH 2/8] external-toolchain: better documentation, cleanup, sysroot check Thomas Petazzoni
2009-07-17 8:35 ` [Buildroot] [PATCH 3/8] external toolchain: use LANG=C when calling gcc -v Thomas Petazzoni
2009-07-17 20:50 ` Peter Korsgaard [this message]
2009-07-17 8:35 ` [Buildroot] [PATCH 4/8] external toolchain: more documentation about the principles Thomas Petazzoni
2009-07-17 8:35 ` [Buildroot] [PATCH 5/8] external toolchain: do not copy useless symbolic links Thomas Petazzoni
2009-07-17 8:35 ` [Buildroot] [PATCH 6/8] external toolchain: copy the C++ standard library if needed Thomas Petazzoni
2009-07-17 8:35 ` [Buildroot] [PATCH 7/8] external toolchain: respect $(Q) Thomas Petazzoni
2009-07-17 8:35 ` [Buildroot] [PATCH 8/8] external toolchain: check cross-compiler existence Thomas Petazzoni
2009-07-17 20:53 ` [Buildroot] [pull request] Pull request for branch external-toolchain Peter Korsgaard
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=87ocrjhw4k.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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.