From: Frédéric <fma@gbiloba.org>
To: libffi-discuss@sourceware.org
Subject: Re: Cross-compiling libffi on ppc 603e
Date: Tue, 09 Feb 2016 08:02:00 -0000 [thread overview]
Message-ID: <20160209090223.340b3bc0@gbiloba.org> (raw)
In-Reply-To: <20160203112152.6e7bfb4c@gbiloba.org>
Le 03/02/2016, Frédéric a écrit :
> I cross-compiled Python 2.5.3 for an embedded VME card running a 32bits
> ppc 603e processor:
>
> http://www.dpie.com/vme/cpu-powerpc/men-mikro-a15c
>
> All worked fine, except the _ctypes python module, using libffi, which
> failed with the following error:
>
> In file included from Modules/_ctypes/libffi/src/prep_cif.c:26:
> build/temp.linux2-powerpc-2.7/libffi/include/ffi.h:153:
> #error "no 64-bit data type supported"
>
> (python 2.5.3 uses libffi 3.0.13).
>
> Any idea why I can't cross-compile on this platform? I can see that ppc
> 32bits is supported. I may need to give an additional env. var. to my
> toolchain?
No idea?
--
Frédéric
next prev parent reply other threads:[~2016-02-09 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 10:22 Frédéric
2016-02-09 8:02 ` Frédéric [this message]
2016-02-09 10:41 ` Andrew Haley
2016-02-09 12:45 ` Frédéric
2016-02-09 13:57 ` Andrew Haley
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=20160209090223.340b3bc0@gbiloba.org \
--to=fma@gbiloba.org \
--cc=libffi-discuss@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).