Yes I think this added Enc::AdvancedProcessBlock() function has rough edges. You pointed out one of them, I've stumbled upon another (insufficient screening of the compilation flags - CRYPTOPP_DISABLE_ASM in particular, thus forcing the user of the library to need how exactly the library was compiled - it was not the case with prior versions).
And for you - locate the "malloca.h" file in your system and make sure that rijndael.cpp includes it from the location where it is. As for Wei Dai - perhaps you'd like to reconsider this Enc::ADvancedProcessBlock() construction, as it seems to have broken portability at least on Mac platform. On 4/5/09, anno <[email protected]> wrote: > > hallo everybody, > > I think there is an bug in Crypto++. > > Yesterdy I tried to compile new crypto++ version 5.6.0 with mysys core > (gcc 3.4.5) and I got an error message within compiling the library. > > Here is my error message: > > $ make > g++ -DNDEBUG -g -O2 -pipe -c rijndael.cpp > rijndael.cpp:75:21: malloca.h: No such file or directory > rijndael.cpp: In member function `virtual size_t > CryptoPP::Rijndael::Enc::AdvancedProcessBlocks(const byte*, const > byte*, byte*, size_t, CryptoPP::word32) const': > rijndael.cpp:945: error: `alloca' was not declared in this scope > make: *** [rijndael.o] Error 1 > > In this code area: > > do { > space = (byte *)alloca(255+sizeof(Locals)); > space += (256-(size_t)space%256)%256; > } > while (AliasedWithTable(space, space+sizeof(Locals))); > > Well gcc can not find this "alloca" function in the code. > > best regards anno > > > -- Regards, Uri --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
