Hi, I have no idea if this is caused by bugs in the current gcc 4.1 branch, or if crypto++ 5.2.1 will be needing patching, but this seems like the right place to report the issue.
Attached is the complete build log, and here is a snippet of what seems the most relevant : [...] seckey.h: In function 'void CryptoPP::CheckedSetKey(T*, CryptoPP::CipherDir, const byte*, unsigned int, const CryptoPP::NameValuePairs&) [with T = CryptoPP::BlockCipherFinal<DECRYPTION, CryptoPP::ThreeWay::Dec>]': seckey.h:179: instantiated from 'void CryptoPP::BlockCipherFinal<DIR, BASE>::SetKey(const byte*, unsigned int, const CryptoPP::NameValuePairs&) [with CryptoPP::CipherDir DIR = DECRYPTION, BASE = CryptoPP::ThreeWay::Dec]' 3way.cpp:139: instantiated from here seckey.h:137: error: no matching function for call to 'CryptoPP::BlockCipherFinal<DECRYPTION, CryptoPP::ThreeWay::Dec>::UncheckedSetKey(CryptoPP::CipherDir&, const byte*&, unsigned int&)' 3way.cpp:64: note: candidates are: void CryptoPP::ThreeWay::Base::UncheckedSetKey(CryptoPP::CipherDir, const byte*, unsigned int, unsigned int) [...] Sorry if my email client mangles the above :-( Any help or suggestions welcome. Matthias -- Clean custom Red Hat Linux rpm packages : http://freshrpms.net/ Fedora Core release 4 (Stentz) - Linux kernel 2.6.14-1.1656_FC4 Load : 0.12 0.19 0.20
build.log.gz
Description: GNU Zip compressed data
