[issue29436] Compilation failure against Android NDK r14 beta 2

Xavier de Gaye added the comment: > CPython's support for Android targets only stable releases of the official > NDK. As the NDK is seeing many changes in the recent past and near future (deprecation of the support of gcc in favor of clang, Unified Headers, nearly all the NDK scripts written

[issue29436] Compilation failure against Android NDK r14 beta 2

Chi Hsuan Yen added the comment: Thanks for the response. Sorry if my previous work on Android brings confusion. To prevent possible wasting of time in the future, I'd like to confirm myself for some conclusions: CPython's support for Android targets only stable releases of the official NDK. T

[issue29436] Compilation failure against Android NDK r14 beta 2

Xavier de Gaye added the comment: > For me it's good to fix things as soon as possible. The problem here is that you are attempting to push a change through a PR without providing the other core developers with important information. You should at least have given a reference to issue 29040 an

[issue29436] Compilation failure against Android NDK r14 beta 2

Chi Hsuan Yen added the comment: > Any reason why you do omit mentioning these important facts in the issue ? Both in the title of this issue and that PR, I mention "NDK r14 beta 2". I'm not sure what you're referring to. On IRC, irker states the title first and then the comment content. I bel

[issue29436] Compilation failure against Android NDK r14 beta 2

Xavier de Gaye added the comment: Closing this issue as 'later'. Chi Hsuan Yen, I am still interested by your answers to my questions. -- resolution: -> later stage: -> resolved status: open -> closed ___ Python tracker

[issue29436] Compilation failure against Android NDK r14 beta 2

Xavier de Gaye added the comment: > I've improved the patch and submitted it as PR 159. Now on Android: This is confusing. Android NDK r14 has not been released yet. We do not develop CPython for platform beta releases. Unified headers, the reason for your proposed change, are only introduced in

[issue29436] Compilation failure against Android NDK r14 beta 2

STINNER Victor added the comment: Previously, we asked to not include generated files in patches, like configure. With the new dev process (github, travis), you must now include generated files. -- ___ Python tracker

[issue29436] Compilation failure against Android NDK r14 beta 2

Chi Hsuan Yen added the comment: Well, I have to commit changes to configure and pyconfig.h, otherwise Travis tests fail. Maybe .travis.yml should call autoreconf first. -- ___ Python tracker _

[issue29436] Compilation failure against Android NDK r14 beta 2

Chi Hsuan Yen added the comment: I've improved the patch and submitted it as PR 159. Now on Android: 1. _locale is built 2. _locale has several symbols, including CODESET 3. _locale doesn't have nl_langinfo() Basically _locale maps what langinfo.h does. On Android langinfo.h has several #defin

[issue29436] Compilation failure against Android NDK r14 beta 2

Changes by Chi Hsuan Yen : -- pull_requests: +124 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue29436] Compilation failure against Android NDK r14 beta 2

Chi Hsuan Yen added the comment: Here's a copy of $ANDROID_NDK/sysroot/usr/include/langinfo.h. (/sysroot/ stores unified headers [1]) To use those headers correctly, packagers have to add -D__ANDROID_API__=XY to CPPFLAGS. On the other hand, __ANDROID_API_FUTURE__ is defined in $ANDROID_NDK/sys

[issue29436] Compilation failure against Android NDK r14 beta 2

New submission from Chi Hsuan Yen: Since Android NDK r14 beta 2, unified headers provide langinfo.h but there's no nl_langinfo() in it, causing linking failures: libpython3.7m.a(pylifecycle.o): In function `get_locale_encoding': /home/yen/Projects/python3-android/src/cpython/Python/pylifecycle.