-
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
lxml and requests recipe: build interrupted, "_ctype" error #1700
Comments
Thanks @excepterror for the bug report. Could you share more context of your logs please? |
Full LogI also attached a txt version of it.
|
Thanks for the full log! |
Most certainly, should have done that already, been lazy. I am on to it. |
I also came across that one #1545 mentioning to have system |
Adding cffi produced identical results. libffi-dev is not installed on my system.
Rebuilding with cffi. |
Building the apk succeeded!! So, I have to correct myself: lxml and requests recipes are fine. One thing remains to be checked: If cffi module is needed. I guess not(?) I will check this tomorrow. @AndreMiras, thanks for the help. Your last post was a revelation! |
Glad it works, thanks for the feedback. |
Hello again. The issue described in ticket 815 (posted above) is definitely of the same kind as the one described in this ticket. Thank you, @AndreMiras. |
Versions
Description
The apk build completes successfully with the following requirements: python2, openssl, lxml, requests, kivy. When I try to build with python3 instead, the build fails with error:
The error is produced while the "setuptools" recipe is being built.
The problem seems to be with "lxml" and "requests" modules and/or their dependencies. Without them the apk builds fine.
I wish I had a better explanation. I don't, I am sorry.
I run quite a few tests changing the order of the requirements, messing with the recipes themselves but I always got a 'dependency graph' issue.
I have been following tickets, #1576, #1590, #1617 and #1564. This one seems to be directly related to them.
buildozer.spec
Command:
Spec file:
Logs
The text was updated successfully, but these errors were encountered: