x86_64-pc-linux-gnu-g++ -O2 -march=native -pipe -fPIC -DDISABLE_EMBEDDED_CRYPTOPP=1 -I/usr/include -I/usr/include/python2.7 -c src/pycryptopp/publickey/rsamodule.cpp -o /var/tmp/portage/dev-python/pycryptopp-0.7.1/work/pycryptopp-0.7.1.869544967005693312591928092448767568728501330214-python2_7/temp.linux-x86_64-2.7/src/pycryptopp/publickey/rsamodule.o -w src/pycryptopp/publickey/rsamodule.cpp: In function ‘PyObject* VerifyingKey_serialize(VerifyingKey*, PyObject*)’: src/pycryptopp/publickey/rsamodule.cpp:90:14: error: ‘CryptoPP::TF_SS<CryptoPP::RSA, CryptoPP::PSS, CryptoPP::SHA256, CryptoPP::TF_SS<CryptoPP::RSA, CryptoPP::PSS, CryptoPP::SHA256, int> >::Verifier {aka class CryptoPP::PK_FinalTemplate<CryptoPP::TF_VerifierImpl<CryptoPP::TF_SignatureSchemeOptions<CryptoPP::TF_SS<CryptoPP::RSA, CryptoPP::PSS, CryptoPP::SHA256, int>, CryptoPP::RSA, CryptoPP::PSSR_MEM<false>, CryptoPP::SHA256> > >}’ has no member named ‘DEREncode’ self->k->DEREncode(ss); ^~~~~~~~~ src/pycryptopp/publickey/rsamodule.cpp: In function ‘PyObject* SigningKey_serialize(SigningKey*, PyObject*)’: src/pycryptopp/publickey/rsamodule.cpp:219:14: error: ‘CryptoPP::TF_SS<CryptoPP::RSA, CryptoPP::PSS, CryptoPP::SHA256, CryptoPP::TF_SS<CryptoPP::RSA, CryptoPP::PSS, CryptoPP::SHA256, int> >::Signer {aka class CryptoPP::PK_FinalTemplate<CryptoPP::TF_SignerImpl<CryptoPP::TF_SignatureSchemeOptions<CryptoPP::TF_SS<CryptoPP::RSA, CryptoPP::PSS, CryptoPP::SHA256, int>, CryptoPP::RSA, CryptoPP::PSSR_MEM<false>, CryptoPP::SHA256> > >}’ has no member named ‘DEREncode’ self->k->DEREncode(ss); ^~~~~~~~~ error: command 'x86_64-pc-linux-gnu-g++' failed with exit status 1
Patch linked in the Arch comment works for me after minor modification to adapt it to gentoo: https://gist.github.com/skydrome/bb9665fc0b449167bb25a57b45829ca8
Created attachment 529350 [details, diff] api-change.patch Workaround taken from AUR until new version takes care of the API change.
Hi, Please apply the patch and resolve issue so we can stablize crypto++. Thanks!
(In reply to Alon Bar-Lev from comment #3) > Hi, > Please apply the patch and resolve issue so we can stablize crypto++. > Thanks! ping?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=66ca2f7ff2c8a8f51193d5d75d7f1cc0b77e5a44 commit 66ca2f7ff2c8a8f51193d5d75d7f1cc0b77e5a44 Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2018-10-01 16:59:43 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2018-10-01 16:59:43 +0000 dev-python/pycryptopp: fix building with crypto++-7+ Closes: https://bugs.gentoo.org/654614 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> Package-Manager: Portage-2.3.50, Repoman-2.3.11 .../files/pycryptopp-0.7.1-abi-change.patch | 55 ++++++++++++++++++++++ ...opp-0.7.1.ebuild => pycryptopp-0.7.1-r1.ebuild} | 6 ++- 2 files changed, 59 insertions(+), 2 deletions(-)