This is very helpful.
I had a problem in rijndael.cpp, apparently some kind of namespace issue.
The compiler didn't recognize Rijndael::Dec::AdvancedProcessBlocks
I changed it to Dec::AdvancedProcessBlocks and it seems to compile.

Thanks!
Daniel

On Monday, December 8, 2014 6:50:09 PM UTC+2, Mouse wrote:
>
> I successfully built CryptoPP-5.6.2 on Linux (Ubuntu 14.04 LTS) using GCC 
> 4.8.2, and Mac OS X (multiple versions, up to Mavericks 10.9.5) using GCC 
> 4.8.3 (installed via Macports) and Clang that comes with Xcode 6.1.
>
> I did make a few patches. The most significant one dealt with the build 
> options in the GNUmakefile, which I'm attaching for your convenience.
>
> Note that this makefile includes FHMQV support (the actual code written by 
> Jeffrey Walton, if I'm not mistaken). If you didn't download those sources 
> in addition to cryptopp library, you may need to remove the related lines, 
> or comment them out.
>
> Since you did not list any specific errors, I can't be more specific in 
> telling how to deal with them.
>
> P.S. I hope that my changes for Mac OS X and for newer Intel CPU will get 
> merged into the mainstream.
>
>
> On Mon, Dec 8, 2014 at 9:46 AM, Daniel Farcovich <[email protected] 
> <javascript:>> wrote:
>
>> CryptoPP supports GCC 3.3 - 4.7.
>> I'm using gcc4.8.2 and have some other errors.
>> Daniel
>>
>> On Monday, December 16, 2013 6:05:55 AM UTC+2, Andrew Dolby wrote:
>>>
>>> Hello,
>>>
>>> I built Crypto++ 5.6.2 with GCC 4.8.1 (from MinGW-w64) on Windows.
>>>
>>> I get this error as I try to build my application (also with GCC 4.8.1) 
>>> using Crypto++:
>>>
>>> In file included from ..\..\cryptopp/randpool.h:4:0, 
>>>
>>> from ..\..\cryptopp/osrng.h:10,
>>>
>>> from ..\test\src\test.cpp:8:
>>>
>>> ..\..\cryptopp/cryptlib.h:402:15: warning: unused parameter 'iv' 
>>> [-Wunused-parameter]
>>>
>>> virtual void Resynchronize(const byte *iv, int ivLength=-1) {throw 
>>> NotImplemented(GetAlgorithm().AlgorithmName() + ": this object doesn't 
>>> support resynchronization");}
>>>
>>>
>>> This is how mingw32-make was run:
>>>
>>>
>>> C:/MinGW/mingw64/bin/mingw32-make -f Makefile.Release 
>>>
>>> mingw32-make[1]: Entering directory 'C:/test/bin'
>>>
>>> g++ -c -march=nocona -mtune=core2 -pipe -fno-keep-inline-dllexport -O2 
>>> -frtti -Wall -Wextra -fexceptions -mthreads -DUNICODE -DQT_NO_DEBUG 
>>> -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_OPENGL_ES_2 
>>> -DQT_OPENGL_ES_2_ANGLE -DQT_NEEDS_QMAIN -I..\test -I"..\..\cryptopp" 
>>> -I"..\..\Qt\Qt64-5.1.0\include" -I"..\..\Qt\Qt64-5.1.0\include\QtWidgets" 
>>> -I"..\..\Qt\Qt64-5.1.0\include\QtGui" 
>>> -I"..\..\Qt\Qt64-5.1.0\include\QtANGLE" 
>>> -I"..\..\Qt\Qt64-5.1.0\include\QtCore" -I"release" -I"." 
>>> -I"..\..\Qt\Qt64-5.1.0\mkspecs\win32-g++" -o release\test.o 
>>> ..\test\src\test.cpp
>>>
>>> When I compiled Crypto++ I got no errors, though I was originally 
>>> getting Resynchronize errors when I tried to build it with a different 
>>> compiler.
>>>
>>> Thanks,
>>>
>>> Andrew Dolby
>>>
>>  -- 
>> -- 
>> You received this message because you are subscribed to the "Crypto++ 
>> Users" Google Group.
>> To unsubscribe, send an email to [email protected] 
>> <javascript:>.
>> More information about Crypto++ and this group is available at 
>> http://www.cryptopp.com.
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Crypto++ Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Regards,
> Mouse
>
>  

-- 
-- 
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.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to