Kivy(Buildozer) compilation with Openssl stop due to a peculiar building error

230 views
Skip to first unread message

Samy Lahfa

unread,
Mar 19, 2017, 9:56:36 PM3/19/17
to kivy-...@googlegroups.com
So I am trying to build(with buildozer) a simple app for android, with Openssl and it doesn't work, I'm on Archlinux, and I use Python 2.7, I have another Python, Python 3.6 but I don't think they're colliding.
I have replaced my account's name by xxxxx just for security purposes, and I'm not using any Virtualenv.
I have this error that shows up at the last lines of the log :
which: no virtualenv-2.7 in (/home/xxxxx/.buildozer/android/platform/apache-ant-1.9.4/bin:/home/xxxxx/.rvm/gems/ruby-2.0.0-p648/bin:/home/xxxxx/.rvm/gems/ruby-2.0.0-p648@global/bin:/home/xxxxx/.rvm/rubies/ruby-2.0.0-p648/bin:/home/xxxxx/.rvm/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
which: no virtualenv2.7 in (/home/xxxxx/.buildozer/android/platform/apache-ant-1.9.4/bin:/home/xxxxx/.rvm/gems/ruby-2.0.0-p648/bin:/home/xxxxx/.rvm/gems/ruby-2.0.0-p648@global/bin:/home/xxxxx/.rvm/rubies/ruby-2.0.0-p648/bin:/home/xxxxx/.rvm/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
which: no virtualenv2 in (/home/xxxxx/.buildozer/android/platform/apache-ant-1.9.4/bin:/home/xxxx/.rvm/gems/ruby-2.0.0-p648/bin:/home/xxxxx/.rvm/gems/ruby-2.0.0-p648@global/bin:/home/xxxxx/.rvm/rubies/ruby-2.0.0-p648/bin:/home/xxxxx/.rvm/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
which: no cython2 in (/home/xxxxxx/.buildozer/android/platform/apache-ant-1.9.4/bin:/home/xxxxxx/.rvm/gems/ruby-2.0.0-p648/bin:/home/xxxxx/.rvm/gems/ruby-2.0.0-p648@global/bin:/home/xxxxxx/.rvm/rubies/ruby-2.0.0-p648/bin:/home/xxxxx/.rvm/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
./distribute.sh: ligne 291: lsb_release : commande introuvable
/home/xxxxx/Projects/Python/KivyApp/Test02/.buildozer/android/platform/python-for-android/build/python-install/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'zip_safe'
  warnings.warn(msg)
OpenSSL/crypto/crl.c:6:23: error: static declaration of 'X509_REVOKED_dup' follows non-static declaration
 static X509_REVOKED * X509_REVOKED_dup(X509_REVOKED *orig) {
                       ^
In file included from /home/xxxxx/Projects/Python/KivyApp/Test02/.buildozer/android/platform/python-for-android/build/openssl/openssl-1.0.2h/include/openssl/ssl.h:156:0,
                 from OpenSSL/crypto/x509.h:17,
                 from OpenSSL/crypto/crypto.h:30,
                 from OpenSSL/crypto/crl.c:3:
/home/xxxxx/Projects/Python/KivyApp/Test02/.buildozer/android/platform/python-for-android/build/openssl/openssl-1.0.2h/include/openssl/x509.h:751:15: note: previous declaration of 'X509_REVOKED_dup' was here
 X509_REVOKED *X509_REVOKED_dup(X509_REVOKED *rev);
               ^
error: command 'arm-linux-androideabi-gcc' failed with exit status 1

It seems it is from the building of openssl but if someone could help me get further down this issue and get the root of the problem it will be a big help.
Also, I need to build openssl because my app needs to import _ssl, if there is another way to import _ssl feel free to tell me.
logsofbuildozer

alexbr...@gmail.com

unread,
Mar 20, 2017, 2:02:20 AM3/20/17
to Kivy users support
Try to add futures and requests after openssl in your buildoser.specs

Samy Lahfa

unread,
Mar 20, 2017, 6:26:31 AM3/20/17
to Kivy users support
It is still the same error, it seems to be while building the pyopenssl module the build fails due to some weird declaration in the building of the module.

Samy Lahfa

unread,
Mar 21, 2017, 1:52:57 PM3/21/17
to Kivy users support
So apparently the fix to this issue is here : https://groups.google.com/forum/#!topic/kivy-users/Qt0jNIOACZc
It works now just by changing the  C code, and rebuilding.
Reply all
Reply to author
Forward
0 new messages