The latest stable release of m2crypto is 0.15, but the latest version in Portage still is 0.13.1. 0.16 is going to be released around end of June, BTW.
Does it fix Bug 95559, by chance? :)
Created attachment 88214 [details, diff] Patch to upgrade m2crypto-0.13.ebuild to m2crypto-0.15.ebuild With this patch, m2crypto-0.15 builds fine for me. /usr/share/doc/m2crypto-0.15/example/[dr]satest.py produce no errors. I haven't done any other test, though.
Created attachment 88246 [details, diff] Patch to upgrade m2crypto-0.15.ebuild to m2crypto-0.16_beta1.ebuild 0.16beta1 has important improvements (like support for RSA.sign and RSA.verify) I need.
Both 0.15 and 0.16beta1 work fine for my purposes (mostly RSA sign&verify), BTW. Running the tlslite tests (tls.py {server,client}test) didn't show any problem, either (only tested for 0.16beta1). tlslite is the only package in Portage using m2crypto.
Added 0.16 to the tree. Thanks all.