On Tue, 14 Jul 2015 10:22:05 -, Andrew Robinson andr...@r3dsolutions.com
wrote:
I'm trying to cross compile C-python 2.7.10 for an embedded system. (Eg:
a Kobo reader).
But there appears to be some bugs that do not allow the latest
maintenance release of Python to correctly cross
Hi.
I'm trying to cross compile C-python 2.7.10 for an embedded system. (Eg:
a Kobo reader).
But there appears to be some bugs that do not allow the latest
maintenance release of Python to correctly cross compile on an x86-64
build system, for a 32 bit arm system.
I have researched the
Frank, Matthew I matthew.i.frank at intel.com writes:
4. Module _decimal is failing to compile. The problem is that it has
a header called memory.h. Android's libc has the problem that
/usr/include/stdlib.h includes memory.h. But the build system
puts -I. on the include path
Hi Frank,
Nobody has responded to you yet, but don't feel discouraged by that! The
core Python development group consists mostly of people who don't develop
mobile apps in their day jobs, and they may feel reluctant to maintain
changes that they can't personally test. (And I don't expect it would
This email is about my experience getting CPython (3.4.1) to
cross-compile and run on x86 Android (4.4.2 with sdk 19 and ndk-r9).
I know that Android is not a supported architecture (and I won't
regale you with stories about the complete locale and mbstowcs support
I had to borrow from FreeBSD to
On 30.06.2012 23:17, Antoine Pitrou wrote:
Hello,
I think these patches are premature (they break compilation on OS X,
and they break ctypes configure on my Linux box).
that was unrelated. fixed last night.
Furthermore, they
were committed post-beta, which means they should probably
On Sun, Jul 1, 2012 at 6:22 PM, Matthias Klose d...@ubuntu.com wrote:
the first cross-build fixes went in in April, please consider these fixes for
the then incomplete cros-build fixes. The build issues you did see last night,
were fixed for the OS X build, and I reverted the update for the
On 01.07.2012 10:22, Matthias Klose wrote:
On 30.06.2012 23:17, Antoine Pitrou wrote:
Hello,
I think these patches are premature (they break compilation on OS X,
and they break ctypes configure on my Linux box).
that was unrelated. fixed last night.
It's also something the buildbots can
On Sun, 01 Jul 2012 11:37:50 +0200
Georg Brandl g.bra...@gmx.net wrote:
the first cross-build fixes went in in April, please consider these fixes
for
the then incomplete cros-build fixes. The build issues you did see last
night,
were fixed for the OS X build, and I reverted the
Hello,
I think these patches are premature (they break compilation on OS X,
and they break ctypes configure on my Linux box). Furthermore, they
were committed post-beta, which means they should probably have waited
for after the 3.3 release. So I propose for these commits to be
reverted.
(to be
On Wed, Jun 6, 2012 at 12:35 AM, Terry Reedy tjre...@udel.edu wrote:
On 6/5/2012 4:24 PM, Tarek Sheasha wrote:
Hello,
I have been working for a long time on cross-compiling python for
android I have used projects like:
http://code.google.com/p/android-python27/
I am stuck in a certain
Hello,
I have been working for a long time on cross-compiling python for android I
have used projects like:
http://code.google.com/p/android-python27/
I am stuck in a certain area, when I am cross-compiling python I would like
to install SIP and PyQt4 on the cross-compiled python, I have tried
On 6/5/2012 4:24 PM, Tarek Sheasha wrote:
Hello,
I have been working for a long time on cross-compiling python for
android I have used projects like:
http://code.google.com/p/android-python27/
I am stuck in a certain area, when I am cross-compiling python I would
like to install SIP and PyQt4
Hi All,
I have to cross compile Python to run on Arm processor based MontaVista
Linux.
If anyone has tried this already, please let me know the procedure.
Thanks in advance,
Regards,
Kumar
___
Python-Dev mailing list
Python-Dev@python.org
I have to cross compile Python to run on Arm processor based MontaVista
Linux.
If anyone has tried this already, please let me know the procedure.
Dear Kiran,
The python-dev mailing list is for the development *of* Python, not for
the development *with* Python; use python-list@python.org
We've been having some issues and discussions at work about cross
compiling. There are various people that have tried (are) cross
compiling python. Right now the support kinda sucks due to a couple
of reasons.
First, distutils is required to build all the modules. This means
that python must
I know some folks have successfully used cross-compilation before. But
this was in a distant past. There was some support for it in the
configure script; surely you're using that? I believe it lets you
specify defaults for the TRY_RUN macros. But it's probably very
primitive.
About using
On 11/7/05, Guido van Rossum [EMAIL PROTECTED] wrote:
About using distutils to build the extensions, this is because some
extensions require quite a bit of logic to determine the build
commands (e.g. look at BSDDB or Tkinter). There was a pre-distutils
way of building extensions using
On 11/7/05, Neal Norwitz [EMAIL PROTECTED] wrote:
We've been having some issues and discussions at work about cross
compiling. There are various people that have tried (are) cross
compiling python. Right now the support kinda sucks due to a couple
of reasons.
This might make a good sprint
On Mon, 2005-11-07 at 16:38, Jeremy Hylton wrote:
I think part of the problem is that setup.py has a bunch of heuristics
that are intended to do the right thing without user intervention.
If, on the other hand, the user wants to intervene, because the right
thing is wrong for
Neal Norwitz wrote:
First, distutils is required to build all the modules.
As Guido already suggests, this assertion is false. In a
cross-compilation environment, I would try to avoid distutils,
and indeed, the build process to do so is still supported.
Second, in configure we try to run
Jeremy Hylton wrote:
I think part of the problem is that setup.py has a bunch of heuristics
that are intended to do the right thing without user intervention.
If, on the other hand, the user wants to intervene, because the right
thing is wrong for cross-compiling, you are kind of stuck. I
is this the right place to ask:
How could I build the python interpreter for an embedded linux target system
(arm9 based), cross-compiling on a linux PC host?
thanks, Giovanni Angeli.
___
Python-Dev mailing list
Python-Dev@python.org
There's a patch on sourceforge for cross compiling. I haven't used it
personally.
http://sourceforge.net/tracker/index.php?func=detailaid=1006238group_id=5470atid=305470
Jeff
pgpzVmD49shTu.pgp
Description: PGP signature
___
Python-Dev mailing list
[EMAIL PROTECTED] wrote:
How could I build the python interpreter for an embedded linux target system
(arm9 based), cross-compiling on a linux PC host?
No. news:comp.lang.python (aka: mailto:python-list@python.org) would be
the right list.
This would be the right list for the question I made
25 matches
Mail list logo
