Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Sébastien Royen" <sebastien.royen@armadeus.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python modules search in non english locale (zlib, ...)
Date: Sat, 28 Mar 2015 00:07:24 +0100	[thread overview]
Message-ID: <5515E2AC.3010100@armadeus.com> (raw)

setup.py: do not add crosscompile header locations if language is not
english

With buildroot toolchain, gcc can be multi language.
Python package setup.py need gcc english output to work fine. (find zlib
for example)
We force language to en_US for the need of output parsing.

Signed-off-by: Sebastien Royen <sebastien.royen@armadeus.com>
Index: b/setup.py
===================================================================
--- a/setup.py    2015-03-27 23:55:53.738987211 +0100
+++ b/setup.py    2015-03-27 23:44:48.482968892 +0100
@@ -414,7 +414,7 @@
         tmpfile = os.path.join(self.build_temp, 'gccpaths')
         if not os.path.exists(self.build_temp):
             os.makedirs(self.build_temp)
-        ret = os.system('%s -E -v - </dev/null 2>%s 1>/dev/null' %
(gcc, tmpfile))
+        ret = os.system('LANGUAGE=en_US %s -E -v - </dev/null 2>%s
1>/dev/null' % (gcc, tmpfile))
         is_gcc = False
         in_incdirs = False
         inc_dirs = []

             reply	other threads:[~2015-03-27 23:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 23:07 Sébastien Royen [this message]
2015-03-29 12:46 ` [Buildroot] [PATCH] python modules search in non english locale (zlib, ...) Thomas Petazzoni
2015-03-29 19:08   ` Sébastien Royen
2015-03-29 20:40     ` Thomas Petazzoni
2015-03-30 11:05       ` Yegor Yefremov
2015-03-30 11:49         ` Thomas Petazzoni
2015-03-30 13:37           ` Yegor Yefremov
2015-03-30 14:05             ` Yegor Yefremov
2015-03-31  9:05               ` Yegor Yefremov
2015-03-31  9:32                 ` Sébastien Royen

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=5515E2AC.3010100@armadeus.com \
    --to=sebastien.royen@armadeus.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