[issue28542] document cross compilation

Martin Panter added the comment: Actually I think it is good to document DESTDIR (you weren’t seem aware of it before?). I was just pointing out that it is useful to more than just Android. Perhaps Guido shouldn’t have trimmed it from the 2.7 readme (original text:

[issue28542] document cross compilation

fix, etc are not specific to cross compilation or Android. I must be seeing everything through my little Android hammer these days :) This new patch removes the last paragraph. -- Added file: http://bugs.python.org/file45319/readme_5.patch ___ Python trac

[issue28542] document cross compilation

Martin Panter added the comment: Regarding 2.7, I guess it depends on your definition of “support”. People have been cross-compiling Python 2.7 longer than I have been working on Python. In the past I have tried to apply cross compilation fixes to 2.7. But if you are only confident about 3.6

[issue28542] document cross compilation

Xavier de Gaye added the comment: New patch, less verbose and taking into account the previous posts. -- Added file: http://bugs.python.org/file45294/readme_4.patch ___ Python tracker

[issue28542] document cross compilation

Xavier de Gaye added the comment: > The ACTION-IF-CROSS-COMPILING parameter of the AC_RUN_IFELSE that checks for > getaddrinfo is $ac_cv_buggy_getaddrinfo="no -- configured with > --(en|dis)able-ipv6". Hum, I should have written: The ACTION-IF-CROSS-COMPILING parameter of the AC_RUN_IFELSE

[issue28542] document cross compilation

Xavier de Gaye added the comment: One must also add '--(en|dis)able-ipv6' to configure, otherwise configure exits with: Fatal: You must get working getaddrinfo() function. or you can specify "--disable-ipv6". The ACTION-IF-CROSS-COMPILING parameter of the AC_RUN_IFELSE that checks

[issue28542] document cross compilation

Xavier de Gaye added the comment: I have changed my Android build system to use DESTDIR, it is simpler than using 'mount --bind'. Thanks for the suggestion Martin. Here is a new patch adding some text for the Android cross compilation. -- Added file: http://bugs.python.org/file45268

[issue28542] document cross compilation

Xavier de Gaye added the comment: New patch. -- Added file: http://bugs.python.org/file45263/readme_2.patch ___ Python tracker ___

[issue28542] document cross compilation

(with sudo) and use 'sudo mount --bind $INSTALL_ROOT /sdcard' so that 'make install' actually copies the files to $INSTALL_ROOT and so that the modules are byte compiled modules with the proper '-d' option to compileall. This allows also for multiple cross-compilation using different $INSTALL_ROOT d

[issue28542] document cross compilation

Martin Panter added the comment: Thanks, this looks like a decent start. I’m not that familiar with cross-compiling Python, but here are a couple questions: $(cd /path/to/source && pwd)/configure Why do you use $(pwd) here? I have mainly seen relative paths used (my own experiments, and

[issue28542] document cross compilation

Changes by Xavier de Gaye : -- components: +Cross-Build, Documentation nosy: +Alex.Willmer ___ Python tracker ___

[issue28542] document cross compilation

New submission from Xavier de Gaye: Patch adding a section to the README. -- assignee: xdegaye files: readme.patch keywords: patch messages: 279532 nosy: xdegaye priority: normal severity: normal stage: patch review status: open title: document cross compilation type: enhancement

[issue28538] _socket module cross-compilation error on android-24

path/to/android/cpython/Modules/socketmodule.c:6240:12: note: forward declaration of 'struct if_nameindex' struct if_nameindex *ni; ^ 6 warnings and 3 errors generated. -- messages: 279495 nosy: xdegaye priority: normal severity: normal stage: needs patch status: open titl

[issue28018] Cross compilation fails in regen

Chi Hsuan Yen added the comment: Closing, regen is not used anymore after issue28046 landed. -- resolution: -> not a bug status: open -> closed ___ Python tracker

[issue28018] Cross compilation fails in regen

New submission from Chi Hsuan Yen: Since issue23968 landed (changeset 5c77488830bc), cross compilation fails. It's not regression of a single revision but is caused by a combination of multiple changes. Here are my steps: 1. git clone https://github.com/yan12125/python3-android 2. comment

[issue27453] Fix cross-compilation with Android NDK and Clang

Chi Hsuan Yen added the comment: Several days ago I have once tried to set CC="clang -target $(TARGET) -gcc-toolchain $(GCC_TOOLCHAIN)", and it failed to build some dependency of Python (I can't remember). Just tried and everything is OK. Dunno what's changed. Anyway both approaches (-target

[issue27453] Fix cross-compilation with Android NDK and Clang

Xavier de Gaye added the comment: With configure run as './configure CC="$(CC)" ...' and when CC is set to: CC = clang --sysroot=$(SYSROOT) -target $(TARGET) -gcc-toolchain $(GCC_TOOLCHAIN) and building for armv7 on android-21, then configure runs $CPP as: checking for CPP... clang

[issue27453] Fix cross-compilation with Android NDK and Clang

s $(PLATFORM_TRIPLET) detection. [1] https://developer.android.com/ndk/downloads/revision_history.html -- components: Cross-Build files: ndk-clang-preprocessor.patch keywords: patch messages: 269816 nosy: Alex.Willmer, Chi Hsuan Yen, xdegaye priority: normal severity: normal status: open title: F

[issue23670] Modifications to support iOS as a cross-compilation target

Changes by Chris Rebert : -- nosy: +cvrebert ___ Python tracker ___ ___

[issue26884] android: cross-compilation of extension module links to the wrong python library

Changes by Matthias Klose : -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue26884] android: cross-compilation of extension module links to the wrong python library

Roundup Robot added the comment: New changeset d00837de03d7 by doko in branch '3.5': - Issue #26884: Fix linking extension modules for cross builds. https://hg.python.org/cpython/rev/d00837de03d7 -- nosy: +python-dev ___ Python tracker

[issue23670] Modifications to support iOS as a cross-compilation target

Luke Taylor added the comment: Ok, great! On Fri, Jun 3, 2016 at 7:34 AM Luke Taylor wrote: > Ah, cool! > On Fri, Jun 3, 2016 at 2:58 AM Russell Keith-Magee > wrote: > >> >> Russell Keith-Magee added the comment: >> >> Yes - I'm aware of

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Yes - I'm aware of Pythonista; the author of that app contracted me to develop the 3.5 patch that is attached to this ticket :-) -- ___ Python tracker

[issue23670] Modifications to support iOS as a cross-compilation target

Luke Taylor added the comment: Are you aware of Pythonista? I have no affiliation, but I'm a fan of the app and the community surrounding it. See http://omz-software.com/pythonista/ for details. I'm sure communication with the developer of the app could yield some useful insights. --

[issue26884] android: cross-compilation of extension module links to the wrong python library

Xavier de Gaye added the comment: Another description of the problem: * On the build system, the native python (in one of the search directories of PATH) has been built without --with-pydebug. * The cross-compilation is done on this build system with --with-pydebug. * The cross-compilation

[issue26884] android: cross-compilation of extension module links to the wrong python library

Changes by Xavier de Gaye <xdeg...@gmail.com>: -- title: cross-compilation of extension module links to the wrong python library -> android: cross-compilation of extension module links to the wrong python library ___ Python tra

[issue26884] cross-compilation of extension module links to the wrong python library

Changes by Xavier de Gaye : -- nosy: +dstufft, eric.araujo ___ Python tracker ___ ___

[issue26884] cross-compilation of extension module links to the wrong python library

New submission from Xavier de Gaye: configure of the cross compilation is run with '--enable-shared --with-pydebug'. The cross-compilation fails attempting to link the extension module objects with a non existing libpython3.6m instead of libpython3.6dm, when the native python that is used

[issue20306] Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail

Stefan Krah added the comment: Okay, for the record: I think that returning "None" would probably be more correct than the empty string, but I don't think users actually care to the point that they will introduce a case split in their applications. Realistically, probably no one cares about

[issue20306] Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail

Roundup Robot added the comment: New changeset f0f519aca558 by Stefan Krah in branch 'default': Issue #20306: Android is the only system that returns NULL for the pw_passwd https://hg.python.org/cpython/rev/f0f519aca558 -- ___ Python tracker

[issue20306] Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail

Xavier de Gaye added the comment: With changeset 0d74d4937ab9, test_pwd fails on android API level 21 at test_values with: Traceback (most recent call last): File "/sdcard/org.bitbucket.pyona/lib/python3.6/test/test_pwd.py", line 27, in test_values

[issue20306] Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail

Changes by Stefan Krah : -- assignee: -> skrah components: +Build -Cross-Build nosy: +skrah resolution: -> fixed stage: -> resolved status: open -> closed versions: +Python 3.6 -Python 3.4, Python 3.5 ___ Python tracker

[issue20306] Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail

Roundup Robot added the comment: New changeset 0d74d4937ab9 by Stefan Krah in branch 'default': Issue #20306: The pw_gecos and pw_passwd fields are not required by POSIX. https://hg.python.org/cpython/rev/0d74d4937ab9 -- nosy: +python-dev ___ Python

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Stefan Krah added the comment: Thank you, closing this. -- resolution: -> out of date stage: -> resolved status: open -> closed versions: +Python 3.6 -Python 3.4 ___ Python tracker

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Xavier de Gaye added the comment: This error: _curses.error: setupterm: could not find terminfo database does not occur for me after removing the '--disable-database --disable-home-terminfo' options from the configure options used to cross-compile ncurses, and after setting the TERMINFO

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Chi Hsuan Yen added the comment: curses was broken and now it's fixed. Yes - Android's locale patch is no longer necessary in _curses either. However, there are runtime errors: shell@ASUS_Z00E_2:/data/local/tmp $ python3.6 -c 'import curses; curses.initscr()'

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Stefan Krah added the comment: Thank you, this is excellent! Does that mean that all locale patches are no longer needed? Here is one left (perhaps accidentally): https://github.com/yan12125/python3-android/blob/cpython-hg/mk/ncurses/android-locale-fixes.patch --

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Chi Hsuan Yen added the comment: Android NDK provides an "android-support" package [1]. There is no documentation other than README in its git repository, I guess it's a 'compatibility layer' between applications targetting a complete C library and Android's BioniC. With my patchset [2],

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Alex - The usual cause for that problem isn't regrtest (at least, not directly). The cause is one of the tests in the suite spawning a subprocess. Due to the way the test harness works, when the test suite forks/spawns a subprocess (e.g., to run a

[issue22699] cross-compilation of Python3.4

Changes by Alex Willmer : -- nosy: +Alex.Willmer ___ Python tracker ___ ___

[issue23670] Modifications to support iOS as a cross-compilation target

Alex Willmer added the comment: I've done my best to rebase Freakboy's patch onto 3.6-dev. The attached applies cleanly, but the testsuite goes into an infinite loop. It's a start at least. At a guess the problem is in Lib/test/libregrtest/ or Lib/test/regrtest.py where the patch changes

[issue23670] Modifications to support iOS as a cross-compilation target

Nick Coghlan added the comment: Mac OS X 10.5 was the last version to support PowerPC architectures, and according to https://en.wikipedia.org/wiki/Mac_OS_X_Leopard#Release_history, the final version of that was 10.5.8, released in August 2009. While we don't have a section in

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Another update - the issue with libffi has been resolved, so there is now only need for a single copy of libffi_ios sources. This directory could potentially be merged with the libffi_osx sources, except that libffi no longer supports PowerPC as a

[issue11365] Integrate Buildroot patches (cross-compilation)

Changes by STINNER Victor : -- resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue22699] cross-compilation of Python3.4

Changes by William Scullin : -- type: resource usage -> compile error ___ Python tracker ___

[issue22699] cross-compilation of Python3.4

William Scullin added the comment: I thought this was originally a help request and was going to re-direct this. Cross-compile with 3.4.3 and later seems broken. Procedure followed: wget https://www.python.org/ftp/python/3.5.0/Python-3.5.0rc1.tgz tar -xf Python-3.5.0rc1.tgz mkdir

[issue23670] Modifications to support iOS as a cross-compilation target

Changes by Cory Benfield c...@lukasa.co.uk: -- nosy: +Lukasa ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23670 ___ ___ Python-bugs-list mailing

[issue23670] Modifications to support iOS as a cross-compilation target

Changes by Marco Paolini markopaol...@gmail.com: -- nosy: +mpaolini ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23670 ___ ___ Python-bugs-list

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Another update - this time, there are only 4 failing tests on device, all related to ctypes issues. The sample Xcode project and iOS-test harness have been modified, simplifying the project layout, and using Apple-preferred directories for resources

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Another patch update - the code now passes the full Python test suite on the iOS simulator. There are still a couple of failures on device; as before, these appear to be due to ctypes problems and a permissions issue with os.mkdir. -- Added

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: This new patch (20150504.diff) adds support for running the Python test suite The new patch is standalone, and contains everything in the previous patch. An XCode project (Tools/iOS-test) has been added to the source tree; this project contains bootstrap

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Here's an updated patch that integrates some of the feedback that has been received so far. Notable changes: * The code now works for ARMv7. Unfortunately, the price for this is a new libffi_ios_aarch source directory, containing generated source tree

[issue23670] Modifications to support iOS as a cross-compilation target

Matthias Klose added the comment: not reviewing everything, but - libffi_ios* will be bitrot. I understand that you'll need an unreleased version, however I would much prefer that any additional patches are added in the repo, and maybe then patching libffi from the iOS build

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Hi Matthias: * The libffi situation on iOS is much the same as it is on OS/X - it needs to be pre-generated. This can't be driven by the existing build system - libffi's Makefile requires a separate pre-generation step. There's certainly potential for

[issue23670] Modifications to support iOS as a cross-compilation target

Changes by Ned Deily n...@acm.org: -- assignee: - ned.deily stage: - patch review versions: +Python 3.5 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23670 ___

[issue23670] Modifications to support iOS as a cross-compilation target

Ned Deily added the comment: Russell, we talked a bit about this topic at the Python Language Summit today (after watching your excellent video). I think there was general agreement there that having iOS support would be a good thing along with the recognition that the requirements for

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Nick: Finding a way to get on-device test results is next on my TODO list, once I've got the patch up to date for trunk. FYI - Updating to trunk is currently blocking on issue22625 (which was introduced by the fix for issue22359). I had thought about

[issue23670] Modifications to support iOS as a cross-compilation target

Nick Coghlan added the comment: (Some work on the Buildbot site would still be required, but it would be triggering a Sauce Labs run rather than managing the mobile hardware directly) -- ___ Python tracker rep...@bugs.python.org

[issue23670] Modifications to support iOS as a cross-compilation target

Nick Coghlan added the comment: Rather than trying to do something ourselves on the mobile testing front, we may want to instead explore the free-for-open-source-project offering from Sauce Labs: https://saucelabs.com/opensauce/ Adapting that to run the CPython self-tests as an app might be

[issue23670] Modifications to support iOS as a cross-compilation target

R. David Murray added the comment: The Sauce labs option may render this obsolete, but to answer your question, Russell: our buildbot fleet is distributed in many people's offices, basements, and occasionally colo racks. The buildbot needs to be on-line 24/7, but it calls out and does not

[issue23670] Modifications to support iOS as a cross-compilation target

Ned Deily added the comment: Ack, much to consider. Adding doko as I believe he has been most closely following developments with libffi releases. -- nosy: +doko ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23670

[issue23670] Modifications to support iOS as a cross-compilation target

Ned Deily added the comment: As a cross-compilation target. From a first quick look at it, it appears the patch requires a current Mac OS X system to build for iOS; the necessary standard build tools and SDKs for iOS are only available on OS X. These are the same build tools used for OS X

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Nick: you are correct - these are changes to support iOS as a cross-compilation target, so you can run your Python code on an iOS device. Apologies for the confusion in nomenclature. Ned: You're correct that the build needs to be run on an OS/X machine

[issue23670] Modifications to support iOS as a cross-compilation target

much of the framework build specific steps scattered throughout the Makefile *and* it could also simplify and speed up the iOS builds by not du plicating the platform-independent build steps. It might even be a useful abstraction for other non-Apple multiple-arch or cross-compilation builds

[issue23670] Modifications to support iOS as a cross-compilation target

R. David Murray added the comment: Also remember that being a supported platform requires buildbots. If I'm reading this right that means two: one for the simulator build, and one that actually runs on the device (once the run-the-test issues is solved). I'm not sure what would need to be

[issue23670] Modifications to support iOS as a cross-compilation target

Russell Keith-Magee added the comment: Understood that buildbots are required. The subject has come up a couple of times on mobile-sig - however, I haven't got a good answer for exactly what this means in practice. Does build hardware need to be delivered to a specific build farm location, or

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Stefan Krah added the comment: Consider the libmpdec part rejected. It is too much work given that external libmpdecs need to be compatible and Android can use the Python version of decimal. -- nosy: +skrah ___ Python tracker rep...@bugs.python.org

[issue22699] cross-compilation of Python3.4

Changes by William Scullin wscul...@gmail.com: -- nosy: +wscullin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22699 ___ ___ Python-bugs-list

[issue20306] Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail

Matt Frank added the comment: Apologies. That last patch includes diffs to generated files (configure and pyconfig.h.in). This version just patches Modules/pwdmodule.c and configure.ac. After applying the patch please run autoheader and autoconf to correctly regenerate configure and

[issue20306] Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail

Changes by Matt Frank matthew.i.fr...@intel.com: -- nosy: +freakboy3742 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20306 ___ ___

[issue20306] Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail

Changes by Matt Frank matthew.i.fr...@intel.com: -- nosy: +WanderingLogic ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20306 ___ ___

[issue20306] Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail

Matt Frank added the comment: Here is shiz's patch extended with the addition to configure.ac. I added the variable HAVE_PASSWD_GECOS_FIELD and the appropriate tests. Luckily this very problem (missing pw_gecos field) is the example used in the autoconf manual

[issue22699] cross-compilation of Python3.4

New submission from Billy: Who knows to cross-compile Python 3.4? -- messages: 229828 nosy: bill9889 priority: normal severity: normal status: open title: cross-compilation of Python3.4 type: resource usage versions: Python 3.4 ___ Python tracker rep

[issue22699] cross-compilation of Python3.4

Changes by STINNER Victor victor.stin...@gmail.com: -- nosy: +doko ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22699 ___ ___ Python-bugs-list

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Changes by Stefan Krah stefan-use...@bytereef.org: -- nosy: -skrah ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20305 ___ ___ Python-bugs-list

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Changes by Stefan Krah stefan-use...@bytereef.org: -- nosy: +lizhenhua ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20305 ___ ___

[issue20306] Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail

Antoine Pitrou added the comment: Interesting. It seems pw_gecos isn't mandated by POSIX: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/pwd.h.html I wonder if there's a better way to do this (autoconf check?) than an Android-specific #ifdef, though. -- nosy: +pitrou

[issue20306] Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail

Shiz added the comment: Ah, yes, if it's not actually mandated by POSIX, something like HAVE_PASSWD_PW_GECOS would be more appropriate. I'll rework the patch into something more generic. -- ___ Python tracker rep...@bugs.python.org

[issue20307] Android's failure to expose SYS_* system call constants causes _posixsubprocess cross-compilation to fail

Roundup Robot added the comment: New changeset 211eeb97b352 by Gregory P. Smith in branch '3.4': Add conditional code for android's lack of definition of SYS_getdent64. http://hg.python.org/cpython/rev/211eeb97b352 New changeset 9f89958ded0a by Gregory P. Smith in branch 'default': Add

[issue20307] Android's failure to expose SYS_* system call constants causes _posixsubprocess cross-compilation to fail

Changes by Gregory P. Smith g...@krypto.org: -- resolution: - fixed stage: - committed/rejected status: open - closed versions: +Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20307

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Stefan Krah added the comment: I've been looking into this, and the only option provided by the Android NDK involves cross-compiling Python on a regular machine. This would require some custom commands before and in between the builds, to build a host Python first, then cross-compile the

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Antoine Pitrou added the comment: I've been looking into this, and the only option provided by the Android NDK involves cross-compiling Python on a regular machine. This would require some custom commands before and in between the builds, to build a host Python first, then cross-compile the

[issue20307] Android's failure to expose SYS_* system call constants causes _posixsubprocess cross-compilation to fail

Changes by Antoine Pitrou pit...@free.fr: -- nosy: +gregory.p.smith ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20307 ___ ___ Python-bugs-list

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Changes by Antoine Pitrou pit...@free.fr: -- nosy: +haypo, skrah ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20305 ___ ___ Python-bugs-list

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Stefan Krah added the comment: I agree with Marc-Andre. Also, we should have an Android buildbot. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20305 ___

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

STINNER Victor added the comment: Is there the only patch required to compile Python 3.4 on Android? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20305 ___

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

somewhat harder as the cross-compilation requires a host Python of the same version, which I didn't have. I formatted a patch which allows the user to supply a special host python path using the HOSTPYTHON environment variable to ./configure. I'll make an issue for that soon, and will bundle

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Stefan Krah added the comment: Shiz rep...@bugs.python.org wrote: As far as maintaining an Android port for CPython goes; I may be interested in this as I'd need to regularly use it anyway. Can anyone tell me what the possibilities are here? There seem to be some external ports already. --

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Shiz added the comment: c) Many (or all) core committers did not have access to the platform in question. I'd say Android is quite a common platform these days, although I'd concur that it's not particularly easy to run Python OOTB on. :) Wikipedia claims that QEMU also powers the

[issue20307] Android's failure to expose SYS_* system call constants causes _posixsubprocess cross-compilation to fail

Gregory P. Smith added the comment: The patch seems reasonable. i'd modify it slightly to include a check the SYS_getdents64 is not already defined before doing the #define. -- assignee: - gregory.p.smith ___ Python tracker rep...@bugs.python.org

[issue20307] Android's failure to expose SYS_* system call constants causes _posixsubprocess cross-compilation to fail

Shiz added the comment: That's probably a good idea. Fixed patch attached. -- Added file: http://bugs.python.org/file33584/Python-3.4.0tip-expose-SYS_getdents64-on-android-v2.patch ___ Python tracker rep...@bugs.python.org

[issue20307] Android's failure to expose SYS_* system call constants causes _posixsubprocess cross-compilation to fail

Shiz added the comment: Please take note of the discussion in issue 20305 if you were planning to merge this, by the way. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20307 ___

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Changes by Shiz h...@shiz.me: -- title: Android's incomplete locale.h implementation prevents compilation - Android's incomplete locale.h implementation prevents cross-compilation ___ Python tracker rep...@bugs.python.org http://bugs.python.org

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Changes by Serhiy Storchaka storch...@gmail.com: -- nosy: +lemburg, loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20305 ___ ___

[issue20306] Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail

files: Python-3.4.0tip-workaround-android-missing-pw_gecos-field.patch keywords: patch messages: 208487 nosy: shiz priority: normal severity: normal status: open title: Lack of pw_gecos field in Android's struct passwd causes cross-compilation for the pwd module to fail type: compile error versions

[issue20307] Android's failure to expose SYS_* system call constants causes _posixsubprocess cross-compilation to fail

_posixsubprocess cross-compilation to fail type: compile error versions: Python 3.4 Added file: http://bugs.python.org/file33551/Python-3.4.0tip-expose-SYS_getdents64-on-android.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20307

[issue20305] Android's incomplete locale.h implementation prevents cross-compilation

Marc-Andre Lemburg added the comment: I'd be +1 on such a patch if we were to officially support Android, but we'd need a volunteer to champion for this (which would be a good thing, IMO). Otherwise, such changes need to be maintained externally. --

[issue20307] Android's failure to expose SYS_* system call constants causes _posixsubprocess cross-compilation to fail

Shiz added the comment: I of course meant the syscall(2) interface, not syscall(1). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20307 ___ ___

[issue3754] cross-compilation support for python build

Matthias Klose added the comment: See http://mail.python.org/pipermail/python-dev/2013-January/123774.html for the discussion. Not updating the patches for tip/trunk is the best way to keep them out of the project. -- ___ Python tracker

[issue3754] cross-compilation support for python build

Greg Hellings added the comment: I'm trying to cross-compile the latest default out of Mercurial based on the status of this. Currently it fails with the following invocation: $ ../configure --host=i686-w64-mingw32 --build=x86_64-redhat-linux-gnu --target=i686-w64-mingw32

<    1   2   3   4   >