-
Notifications
You must be signed in to change notification settings - Fork 514
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
Certain python requirements fail due to _ctypes
#815
Comments
I found a few other modifications that were suggested, but unfortunately it didn't resolve (1) Add That gets libffi to be actually built, but it's not succeeding:
|
Add
@mattrunchey, please, check if that works for you and close this issue if that is the case 😉 |
Almost! Seems to be an error that prevents libffi building - https://stackoverflow.com/questions/6881164/crtbegin-so-o-missing-for-android-toolchain-custom-build ... trying a couple of things real quick.
Which is weird, since the "hacky stuff for linking" copies those files...
I'm going to try it with another android-ndk, but am not hopeful. I can't quite manually try the rebuild within buildozer, but I'm going to see if I can't compile it manually and rule out an ubuntu 18.04 issue. |
Yea, I'm unable to build (use ubuntu:xenail or ubuntu:bionic)
You'll see the debug fail to build libffi, and still fail when trying to use |
Can you add |
Yessir Also, amended my above to include the pip installs for Thank you for the accurate help!! It seems to work now. Hopefully anyone else coming across this problem can use this issue as a way to resolve/path forward :) |
Hi Team, I'm encountering the same issue. Even though I followed the steps provided.
Versions
buildozer.spec
libffi-dev
logs
Can you please advise what else I can try to resolve the issue? Should I open a new issue? |
I have resolved the issue by deleting the .buildozer inside my projects folder then building again. I have a new error, I'll just raise a new issue. Thank you! |
I had the same issue until i cleaned buildozer by this command please tell if this solved the problem |
Is this really resolved? Given that python-for-android downloads libffi as part of the build process, shouldn't it be able to use the libffi that it downloaded? |
Versions
Description
I have created a basic docker image, been running in the shell, just to get a bare metal APK going. The only thing I've changed in the
buildozer.spec
is my python requirements:Essentially, I can successfully build if i take out the
decorator
requirement. This also happens withenum34
. Many other requirements work successfully, such aspython-dateutil
,msgpack
,monotonic
. The last line of the stacktrace suggests there is an issue finding_ctypes
insetuptools
...buildozer.spec
Command:
Spec file: (the exact thing generated by
buildozer init
, except for the additional requirements)Logs
The text was updated successfully, but these errors were encountered: