Closed Onionus007 closed 1 year ago
I am having this same problem intermittently building Python on my jailbroken iOS 13.3 iPhone 6S. Most of the time it’s been working but then it breaks and I can’t pinpoint what I’m doing that breaks it. It seems to have something to do with autoconf, automake, m4, aclocal, and/or libtool.
you can see it all goes wrong near the top of your log after “ MACOSX_DEPLOYMENT_TARGET” perhaps after ANSI C Headers? Everything becomes a no (except cached).
Does rm -rf your autom4te.cache dir help at all? What about autoupdate and/or autoreconf?
I got Python 3.10.1 latest to build easier than ever last week right out of the box, but now it’s failing this manner and I’m perplexed that even a fresh unpack has the same problem.
I had the same problem because of an older clang version in /usr/local/bin
. export CC=/usr/bin/clang
didn't work, I had to rename /usr/local/bin/clang
to /usr/local/bin/clang.off
temporarily.
Ideally there should be an way to specify the C/C++ compiler or xcrun --find clang
should be used to detect it.
EDIT: You can also move /usr/local/bin
to the end of $PATH in the shell you are using.
👋 @Onionus007, we use the issue tracker exclusively for bug reports and feature requests. However, this issue appears to be a support request. Please use our support channels to get help with the project. Let us know if this comment was made in error, and we'll be happy to reopen the issue.
Versions
Description
I am trying to compile a simple python code into a .apk as a way to prepare the compiler for further work, failing miserably in the first stretch
buildozer.spec
Command:
Spec file:
Logs