Was this a release build of the Crypto++ lib or an app using Crypto, specifically, one using the CRC32 facility?
TIA. michael
At 05:53 PM 3/22/2003 -0500, you wrote:
I just did a release build on cygwin with gcc 3.2, and it worked. I used the following options:
-O -DNDEBUG -ffunction-sections -fdata-sections
-O2 caused run-time errors.
On Fri, Mar 21, 2003 at 11:14:51PM -0800, Michael Hunley wrote:
> My app is cross-platform, made using several custom libs as well as
> crypto++. Under Windows (XP home) it is compiled using MSVC6, SP5. Under
> Redhat Linux 8.0 it is compiled using GCC (g++) 3.2.2 from the Boost.Jam
> build system (v1, not v2 if that means anything to you). Under Win32 I
> compile crypto++ as a sub-project in my workspace using the DSP supplied
> from CVS (with the code-gen set to multi-threaded DLL). I am using the
> current of Crypto++ cut from CVS as of this morning (with the Base64 fix,
> thanks). On windows both the debug and release compile & link without any
> issues. Under Linux, my debug builds fine (with a few warnings about
> unused vars), but my release build reports:
> "undefined reference to 'CryptPP::CRC32::CRC32[in-charge]()'; and
> "undefined reference to 'CryptoPP::CRC32::Update(unsigned char
> const *, unsigned)'
> For all the functions I use it in (3 files with a total of 12 functions).
>
> I think this is something in my build setup, but I cannot find anything, so
> I thought it couldn't hurt to ask. Has anyone else run into a similar
> issue? If so, any fixes? Has anyone successfully built an app under GCC
> with the latest CryptoPP (5.1) using CRC32 in release mode (meaning the
> normal full opts, etc). Anyone know of any command line compile link
> settings that might cause this?
>
> thanks for any help.
>
> Michael Hunley
> Senior Engineer
> PocketPurchase, Inc.
