Created attachment 472056 [details] build.log When trying to install dev-python/m2crypto-0.24.0 on x32 multilib, configure fails with: running build_ext building 'M2Crypto.__m2crypto' extension swigging SWIG/_m2crypto.i to SWIG/_m2crypto_wrap.c swig -python -D__x86_64__ -I/usr/include/python2.7 -I/usr/include -I/usr/include/openssl -includeall -modern -builtin -outdir /var/tmp/portage/dev-python/m2crypto-0.24.0/work/M2Crypto-0.24.0-python2_7/lib/M2Crypto -o SWIG/_m2crypto_wrap.c SWIG/_m2crypto.i /usr/include/openssl/opensslconf.h:10: Error: CPP #error ""abi_x86_64 not supported by the package."". Use the -cpperraswarn option to continue swig processing. error: command 'swig' failed with exit status 1 This seems to be a multilib bug, since the requested ABI should be x32, not x86_64. Build log attached.
Created attachment 472058 [details] emerge --info
The newer ebuild (0.25.1-r2) fails with the same error. The modified (though older) ebuild in the gx86-staging overlay works: https://github.com/sjnewbury/gentoo-gx86-staging/blob/master/dev-python/m2crypto/m2crypto-0.22.3.ebuild
This happens on x86 as well, with exactly the same build error about the include from opensslconf.h
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7e1775ec67ba2e4d390c254b5d5a8074d1cacb4d commit 7e1775ec67ba2e4d390c254b5d5a8074d1cacb4d Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2017-11-22 16:27:36 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2017-11-22 16:28:29 +0000 dev-python/m2crypto: fix build on x32 Closes: https://bugs.gentoo.org/617946 Package-Manager: Portage-2.3.15, Repoman-2.3.6_p7 dev-python/m2crypto/Manifest | 10 +++++----- dev-python/m2crypto/m2crypto-0.27.0.ebuild | 8 ++++++++ 2 files changed, 13 insertions(+), 5 deletions(-)
(In reply to tt_1 from comment #3) > This happens on x86 as well, with exactly the same build error about the > include from opensslconf.h That's probably a different issue. I would guess that you are using an x86 chroot, but have not set the Linux personality to i686 using the setarch or linux32 commands.
Exactly, I already figured this out in the meantime. Thanks for the hint about setarch though.
