This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xdegaye
Recipients Alex.Willmer, doko, xdegaye, yan12125
Date 2016-07-05.15:00:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1467730849.29.0.78429659254.issue27453@psf.upfronthosting.co.za>
In-reply-to
Content
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 --sysroot=/opt/android-ndk/platforms/android-21/arch-arm -target armv7-none-linux-androideabi -gcc-toolchain /opt/android-ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64 -E

as can be seen by inserting in configure.ac:
AC_MSG_CHECKING([for CPP])
AC_MSG_RESULT([$CPP])

and the shared libraries are named 'module_name.cpython-36m-arm-linux-gnueabi.so'.

OTOH, the 'configure' script runs its own preprocessings with the following idiom:
if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | $EGREP "memchr" >/dev/null 2>&1; then :

where 'ac_cpp' is set to ac_cpp='$CPP $CPPFLAGS'.
So the proposed patch LGTM.

PLATFORM_TRIPLETs are specific to multiarch systems such as debian and should not be relied upon on Android, but they should not be entirely wrong of course.
History
Date User Action Args
2016-07-05 15:00:49xdegayesetrecipients: + xdegaye, doko, Alex.Willmer, yan12125
2016-07-05 15:00:49xdegayesetmessageid: <1467730849.29.0.78429659254.issue27453@psf.upfronthosting.co.za>
2016-07-05 15:00:49xdegayelinkissue27453 messages
2016-07-05 15:00:48xdegayecreate