Invalid argument to arm-linux-androideabi-gcc

[elijahsgh]

Trying to use python3crystax and buildozer.

If I manually complete the steps mentioned everything seems to work fine - except everything is built as 64-bit. Any hints on what I might be missing?

[INFO]:    Cythonize jnius/jnius.pyx
[INFO]:    -> running cython ./jnius/jnius.pyx
[INFO]:    -> running python3.5 setup.py build_ext -v
()
[INFO]:    STDOUT:                                                             
	/usr/lib/python3.5/site-packages/setuptools/dist.py:364: UserWarning: Normalizing '1.1-dev' to '1.1.dev0'	
  normalized_version,	
running build_ext	
skipping 'jnius/jnius.c' Cython extension (up-to-date)	
building 'jnius' extension	
arm-linux-androideabi-gcc -DANDROID -mandroid -fomit-frame-pointer --sysroot /home/esnyder/.buildozer/android/platform/crystax-ndk-10.3.2/platforms/android-19/arch-arm -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -I/home/esnyder/.buildozer/android/platform/crystax-ndk-10.3.2/sources/python/3.5/include/python -DANDROID -mandroid -fomit-frame-pointer --sysroot /home/esnyder/.buildozer/android/platform/crystax-ndk-10.3.2/platforms/android-19/arch-arm -march=armv7-a -mfloat-abi=softfp -mfpu=vfp -mthumb -fPIC -I/usr/include/python3.5m -c jnius/jnius.c -o build/temp.linux-x86_64-3.5/jnius/jnius.o	
arm-linux-androideabi-gcc: error: unrecognized argument in option '-mtune=generic'	

[dessant]

I believe 32bit is not supported, but @inclement may have more info about this.

[elijahsgh]

So the armeabi binaries are supposed to be 64 bit? Sorry, I'm confused.

I might be missing something here. When I complete the build process and try to run the APK on a device it will tell me that the library has mismatched architecture. The build host is Linux 86_64. I don't know where the mismatch comes from. This happens when using android_new with buildozer. The 'android' build seems to work okay, but I end up with Python 2 and kind of hoped to use the new build tools with Python 3.

[elijahsgh]

Closing, no activity.