From: Julien Boibessot <julien.boibessot@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] Add pygame package
Date: Wed, 11 Jan 2012 10:32:50 +0100 [thread overview]
Message-ID: <4F0D5742.7060803@free.fr> (raw)
In-Reply-To: <87sjjmbpva.fsf@macbook.be.48ers.dk>
On 01/11/2012 09:33 AM, Peter Korsgaard wrote:
> Thanks, looks good. Unfortunately it doesn't work:
>
> building 'pygame.gfxdraw' extension
> creating build/temp.linux-x86_64-2.7
> creating build/temp.linux-x86_64-2.7/src
> creating build/temp.linux-x86_64-2.7/src/SDL_gfx
> /home/peko/source/buildroot/output/host/usr/bin/arm-linux-gcc -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -pipe -Os -fPIC -D_GNU_SOURCE= -D_REENTRANT -I/home/peko/source/buildroot/output/host/usr/arm-unknown-linux-uclibcgnueabi/sysroot/usr/include/SDL -I/home/peko/source/buildroot/output/host/usr/include/python2.7 -c src/gfxdraw.c -o build/temp.linux-x86_64-2.7/src/gfxdraw.o
> In file included from /home/peko/source/buildroot/output/host/usr/include/python2.7/Python.h:8,
> from src/pygame.h:80,
> from src/gfxdraw.c:33:
> /home/peko/source/buildroot/output/host/usr/include/python2.7/pyconfig.h:1136:1: warning: "_GNU_SOURCE" redefined
> <command-line>: warning: this is the location of the previous definition
> In file included from /home/peko/source/buildroot/output/host/usr/arm-unknown-linux-uclibcgnueabi/sysroot/usr/include/limits.h:27,
> from /opt/br/arm926t-wchar/usr/lib/gcc/arm-unknown-linux-uclibcgnueabi/4.3.6/include-fixed/limits.h:122,
> from /opt/br/arm926t-wchar/usr/lib/gcc/arm-unknown-linux-uclibcgnueabi/4.3.6/include-fixed/syslimits.h:7,
> from /opt/br/arm926t-wchar/usr/lib/gcc/arm-unknown-linux-uclibcgnueabi/4.3.6/include-fixed/limits.h:11,
> from /home/peko/source/buildroot/output/host/usr/include/python2.7/Python.h:19,
> from src/pygame.h:80,
> from src/gfxdraw.c:33:
> /home/peko/source/buildroot/output/host/usr/arm-unknown-linux-uclibcgnueabi/sysroot/usr/include/features.h:219:5:
> error: #error It appears you have defined
> _FILE_OFFSET_BITS=64. Unfortunately, uClibc was built without large file
> support enabled.
>
> Notice how it is looking at my host-python rather than target-python
> (where I don't have largefile support) includes.
>
> Any idea?
Oups. I missed that one because error seems to occur only when the Host
is a 64bits architecture (I have a 32 bits Host).
Seems like a problem in distutils that adds
"-I/home/peko/source/buildroot/output/host/usr/include/python2.7" when
compiling, which isn't a problem when Host and Target python
installations match.
You have the same problem (include added) in python-mad package. Does it
compile on your Host ?
Trying to find a solution...
Regards,
Julien
next prev parent reply other threads:[~2012-01-11 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 7:24 [Buildroot] [PATCH v3] Add pygame package julien.boibessot at free.fr
2012-01-11 8:33 ` Peter Korsgaard
2012-01-11 9:32 ` Julien Boibessot [this message]
2012-01-11 9:54 ` Peter Korsgaard
2012-01-11 11:09 ` Julien Boibessot
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=4F0D5742.7060803@free.fr \
--to=julien.boibessot@free.fr \
--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