-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Misconfiguration causing failure in compilation. #2879
Comments
@RobertFlatt Personally I'm using p4a directly without buildozer, and this seems to be the main source of the problem.
|
The easy way to test would be to try with Buildozer. I don't have any other suggestion. |
Hi @ht-thomas , can you please post the full log? |
hey @misl6 ,
These are the arguments are passed to p4a the latest, this is the log from the command line. I tried to write it to a stdout that can record everything in a file but this is all I could collect from the log.
|
Hey @RobertFlatt , |
By latest p4a which branch do you mean? If not |
Thanks @ht-thomas , at the very top of this thread is it says
If that is incorrect and you are not using WSL, then my comment does not apply. |
@HyTurtle the p4a version I'm running is 2023.05.21, the one which was recently released. |
@ht-thomas: Even if you are running on Ubuntu now, is there a chance you are using an NTFS drive volume created in Windows? |
@Julian-O I highly doubt that since the whole machine was formatted. But I think the bug is in the NDK which p4a supports |
Versions
Description
There seems to be an error in the configuration of libffi and GNU Autoconf which causes failure in compiling the python application.
Logs
The text was updated successfully, but these errors were encountered: