From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Python standard library problems
Date: Fri, 12 Aug 2011 17:44:35 +0200 [thread overview]
Message-ID: <4E454A63.6030401@free-electrons.com> (raw)
In-Reply-To: <4E44FA0A.1000902@free-electrons.com>
Ok,
A little update on that.
From my tests, this brokenness occurs only when using a 64-bits system.
32 bits systems are fine, which explains why some have a working python
and other don't.
To complete a bit what I said earlier, in the build log, you have a
bunch of
Include/pyport.h:849:2: error: #error "LONG_BIT definition appears wrong
for platform (bad gcc/glibc config?)."
One for every module that fails to build.
This error comes from the code below in pyport.h
#ifndef LONG_BIT
#define LONG_BIT (8 * SIZEOF_LONG)
#endif
#if LONG_BIT != 8 * SIZEOF_LONG
/* 04-Oct-2000 LONG_BIT is apparently (mis)defined as 64 on some recent
* 32-bit platforms using gcc. We try to catch that here at compile-time
* rather than waiting for integer multiplication to trigger bogus
* overflows.
*/
#error "LONG_BIT definition appears wrong for platform (bad gcc/glibc
config?)."
#endif
LONG_BIT seems correctly defined to 32 in bits/xopen_lim.h of the toolchain.
I'm a bit confused on why this is happening...
On 12/08/2011 12:01, Maxime Ripard wrote:
> Hi all,
>
> With the following config, I have the same problem that Pedro encountered.
>
> When you look closer to the build output, when building python, at the
> end of the process, you have :
>
> Failed to build these modules:
> _bisect _codecs_iso2022 _collections
> _csv _ctypes _ctypes_test
> _elementtree _functools _heapq
> _hotshot _io _json
> _locale _lsprof _md5
> _multibytecodec _multiprocessing _random
> _sha _sha256 _sha512
> _socket _struct _testcapi
> array audioop binascii
> cmath cPickle crypt
> cStringIO datetime dl
> fcntl future_builtins grp
> imageop itertools linuxaudiodev
> math mmap operator
> ossaudiodev parser resource
> select spwd strop
> syslog termios time
> unicodedata
>
> Which is a *lot* of modules. It might be "normal" for some of them, like
> ossaudiodev which is likely to have an unmet dependency, but note that
> all three modules Pedro have mentionned are here.
> Some of them are deprecated too, like imageop.
>
> It would be ideal if we could manage to drop the number of failed build
> modules to 0.
>
> I'll try to look into it.
>
> Maxime
>
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-08-12 15:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 19:18 [Buildroot] Python standard library problems Pedro Sanchez
2011-08-10 21:48 ` Dominic Newton
2011-08-11 13:14 ` Pedro Sanchez
2011-08-11 15:37 ` Dominic Newton
2011-08-11 18:23 ` Pedro Sanchez
2011-08-11 20:54 ` Pedro Sanchez
2011-08-12 10:01 ` Maxime Ripard
2011-08-12 15:44 ` Maxime Ripard [this message]
2011-08-12 17:47 ` Pedro Sanchez
2011-08-16 8:22 ` Maxime Ripard
2011-08-29 15:58 ` Maxime Ripard
2011-08-30 14:36 ` Pedro Sanchez
2011-08-31 14:17 ` Pedro Sanchez
2011-09-01 7:50 ` Thomas Petazzoni
2011-09-01 14:18 ` Pedro Sanchez
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=4E454A63.6030401@free-electrons.com \
--to=maxime.ripard@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