You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...
Run build
Call build_hostpython
Call build_python
Entering in ARM enviromnent
configure: WARNING: if you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used
checking for --enable-universalsdk... no
checking for --with-universal-archs... 32-bit
checking MACHDEP... linux3
checking EXTRAPLATDIR...
checking machine type as reported by uname -m... i686
checking for --without-gcc... no
checking for arm-eabi-gcc... ccache arm-linux-androideabi-gcc -mandroid -fomit-frame-pointer --sysroot /home/martin/work/android/android-ndk-r7/platforms/android-15/arch-arm
checking whether the C compiler works... no
configure: error: in /home/martin/work/android/python-for-android/build/python/Python-2.7.2': configure: error: C compiler cannot create executables Seeconfig.log' for more details
I can report the same issue, fails with androidapi 15, but works fine with 14 may be worth a note or something for anyone new setting up the enviroment.
I was seeing the same "configure: error: C compiler cannot create executables" issue. After a bit of searching and looking at the output log I finally realized it was due to a permission issue. The configure script was trying to copy files to a directory but didn't have proper permissions. I fixed the issue by changing the ownership of the python-for-android directory to my user name. (chown -R "usernmae" python-for-android)
Thought I'd post this here in hopes it'll save someone else a bit of time. :-)
More information for those googlers: You're not constrained to API 14 - you just need to go to android developer website and download the latest NDK (not SDK, NDK) and then upgrade the your environment variables to point to the new NDK location (and new API level) and then re-run ./distribute.sh -m...... And everything works fine.
The easiest way to do it these days is to switch to buildozer instead of
bare python-for-android compiling, and use the default SDK and NDK settings
in buildozer. You don't even need to download the SDK and NDK because
buildozer will get them by itself.
More information for those googlers: You're not constrained to API 14 -
you just need to go to android developer website and download the latest
NDK (not SDK, NDK) and then upgrade the your environment variables to point
to the new NDK location (and new API level) and then re-run ./distribute.sh
-m...... And everything works fine.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-44127057
.
Activity
tito commentedon Jan 9, 2012
What's your Android SDK/NDK ? Did you correctly setup both of them ? Did you download one android platform with SDK android tool ?
mulonemartin commentedon Jan 10, 2012
I switched to androidapi=14 and all went fine. I was using androidapi=15
olymk2 commentedon Jan 16, 2012
I can report the same issue, fails with androidapi 15, but works fine with 14 may be worth a note or something for anyone new setting up the enviroment.
tito commentedon Jan 16, 2012
Ok, after checking, android api 15 cannot be used cause it doesn't exist in NDK r7 (r7 was released before SDK 15). Adding a tip about it in the doc
tito commentedon Jan 17, 2012
added in doc
yurkomik commentedon Apr 15, 2013
Same issue with android api 15 and kivy_stable, kivy compiled ok but had some errors later: import error for lang ets. I have latest SDK and NDK 8.
yihuang commentedon Dec 6, 2013
Same issue here with android api 18 and ndk r8b.
yihuang commentedon Dec 6, 2013
It turns out i need to set api to 14 instead of 18, though the sdk i use is api-18.
sheldonrucker commentedon Dec 31, 2013
I was seeing the same "configure: error: C compiler cannot create executables" issue. After a bit of searching and looking at the output log I finally realized it was due to a permission issue. The configure script was trying to copy files to a directory but didn't have proper permissions. I fixed the issue by changing the ownership of the python-for-android directory to my user name. (chown -R "usernmae" python-for-android)
Thought I'd post this here in hopes it'll save someone else a bit of time. :-)
mraygalaxy commentedon May 25, 2014
More information for those googlers: You're not constrained to API 14 - you just need to go to android developer website and download the latest NDK (not SDK, NDK) and then upgrade the your environment variables to point to the new NDK location (and new API level) and then re-run ./distribute.sh -m...... And everything works fine.
brousch commentedon May 25, 2014
The easiest way to do it these days is to switch to buildozer instead of
bare python-for-android compiling, and use the default SDK and NDK settings
in buildozer. You don't even need to download the SDK and NDK because
buildozer will get them by itself.
On Sun, May 25, 2014 at 5:45 AM, Michael R. Hines
notifications@github.comwrote:
Ben Rousch
brousch@gmail.com
http://clusterbleep.net/
Merge pull request #1 from kivy/master
Merge pull request #1 from kmonson/NdgHttpsClientRecipe
Merge pull request kivy#1 from kivy/master
Pins pyjnius==1.1.2
Merge pull request kivy#1 from dbnicholson/le-home-env
Pins pyjnius==1.1.2
update: replace 'cython' to 'cython~=3.1.2' @pythonforandroid/recipes…
update: replace 'cython' to 'cython~=3.1.2' @pythonforandroid/recipes…