-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build with lxml not working #79
Comments
Well I get no errors during building it via ./distribute.sh -m "lxml kivy" Which NDK / SDK do you use? Have you tried to make a clean build by removing the whole folder and downloading python-for-android, again? |
I was using the NDK r8d and SDK 21.0 when I posted this issue. Now I'm using NDK r8c, but unfortunately, the same error is still there. Yes, so I have. |
Please try to replace the NDK r8d with r8c. I'm not familiar with the changes but try first of all the supported version, before using r8d. |
I replaced the SDK, NDK and python-for-android with new versions of their kin (one of them being the NDK r8c), and it didn't seem to do the trick. Still the same error. When that didn't work I tried installing python-for-android to my laptop and it works like a charm. |
Check your installation again in this case. You probably missed something.. |
Please reopen with the full compilation log, we cannot help with just this error :) |
./distribute.sh -m "lxml kivy"
That command gives the following error message:
-L/home/david/android/python-for-android/build/libs
-L/home/david/android/python-for-android/build/python-install/lib
-lm
-lGLESv2
-lpython2.7
/usr/lib/libpython2.7.so: file not recognized: File format not recognized
collect2: ld returned 1 exit status
I've tried cleaning the git without any success. When that didn't work I tried adding the dependencies to the build:
./distribute.sh -m "libxml2 libxslt python lxml kivy"
Also without success.
It should be noted that I can build distributions without lxml.
The same issue (although with PIL and seems to be fixed) can be found here:
(EDIT: Removed link as it was a completly different issue)
The text was updated successfully, but these errors were encountered: