mirror of
https://github.com/openembedded/meta-openembedded.git
synced 2026-06-14 05:49:57 +00:00
Lukas Bulwahn
dfa33ddb23
After python-m2crypto was reported as failed task in bitbake world on 2014-02-08 by Martin Jansa, I investigated python-m2crypto with MACHINE = "qemux86-64" setting. When compiling python-m2crypto for qemux86-64, the setup.py aborts in the swig call with: | swig -python -I[...]/tmp-eglibc/sysroots/qemux86-64/usr/include/python2.7 -I[...]/tmp-eglibc/sysroots/qemux86-64/usr/include -includeall -o SWIG/_m2crypto_wrap.c SWIG/_m2crypto.i | [...]/tmp-eglibc/sysroots/qemux86-64/usr/include/openssl/opensslconf.h:41: Error: Unable to find 'openssl/opensslconf-32.h' | error: command 'swig' failed with exit status 1 | ERROR: python setup.py build_ext execution failed. | WARNING: exit code 1 from a shell command. To compile for x86-64 architecture, opensslconf.h shall include opensslconf-64.h, not opensslconf-32.h. Properly including opensslconf-64.h can be configured through the bits/wordsize.h header and setting the __x86_64__ directive in the swig call. To set the directive, the SWIG_FEATURES variable for x86-64 is set and exported in the recipe. Compiling python-m2crypto for qemumips still fails and needs further adjustments, but is not addressed here. This patch follows Khem Raj's suggestion on the openembedded-devel mailing list after submission of the first commit to this issue. Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
This layer depends on:
URI: git://github.com/openembedded/oe-core.git
branch: master
revision: HEAD
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
When sending single patches, please use something like:
'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][PATCH'
You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
Main layer maintainer: Koen Kooi <koen@dominion.thruhere.net>
Martin Jansa <martin.jansa@gmail.com>