Nope.. box stock unarchive from the 5.2.1, apply patches by hand, and compile...
I'm going to have to go back to 3.3 for this, I think. Thanks for the help. -=Bob > -----Original Message----- > From: Kevin Hock [mailto:[EMAIL PROTECTED] > Sent: Friday, September 09, 2005 3:27 PM > To: [email protected] > Subject: Re: gcc 4.0 on Mac OS X 10.4 > > > Hi Bob, > > Weird! I applied the patch by hand to 5.2.1 and had no problems at all > compiling. :-/ > > Are you using any custom CFLAGS or LDFLAGS? > > Kevin > > Bob McCown wrote: > > Hi Kevin > > > > I applied the patches by hand and tried to compile via 4.0, but > still was > > getting these errors in 6 files: > > > > > > esign.cpp: In member function `virtual void > > CryptoPP::InvertibleESIGNFunction::GenerateRandom > > (CryptoPP::RandomNumberGenerator&, const CryptoPP::NameValuePairs&)': > > esign.cpp:97: error: cannot allocate an object of abstract type > > 'CryptoPP::NameValuePairs' > > cryptlib.h:222: note: because the following virtual functions are > > pure within 'CryptoPP::NameValuePairs': > > cryptlib.h:303: note: virtual bool > > CryptoPP::NameValuePairs::GetVoidValue(const char*, const > > std::type_info&, void*) const > > make: *** [esign.o] Error 1 > > > > in esign, luc, rabin, rsa, rw, and socketft.cpp. Renaming > those 6 files to > > *.bob allowed the library to compile, but then compiling my app > gave me the > > same kind of link errors at the 3.3 ones below. > > > > I'm stumped as to why I'm getting these link errors, but I also > admit I'm no > > mac developer. I just happened to draw the short straw for the > mac port of > > one of our programs. > > > > -=Bob > > > > > >>-----Original Message----- > >>From: Kevin Hock [mailto:[EMAIL PROTECTED] > >>Sent: Friday, September 09, 2005 2:39 PM > >>To: [email protected] > >>Subject: Re: gcc 4.0 on Mac OS X 10.4 > >> > >> > >>Hi Bob, > >> > >>Yes, 5.2.1 compiles out of the box with GCC 3.3. The patch was only > >>requried for using 4.0. I'm still not sure why you wouldn't just apply > >>it by hand? In fact, you don't even need the huge chunk at the bottom, > >>just the one-liners at the top. > >> > >>Anyway, if you changed compilers, did you rebuild all of your files? > >>Mixing objects from different compiler versions isn't generally a good > >>idea. > >> > >>Kevin > >> > >>Bob McCown wrote: > >> > >>>The continuing saga... > >>> > >>>I changed the makefile to use gcc-3.3, and now libcryptopp.a > build fine. > >>> > >>>But (you knew there was a but) > >>> > >>>I'm getting a raft of linker errors like this: > >>> > >>>/usr/bin/ld: Undefined symbols: > >>>CryptoPP::IteratedHashBase<unsigned > >>>int,CryptoPP::HashTransformation>::PadLastBlock(unsigned > >> > >>int,unsigned char) > >> > >>>CryptoPP::IteratedHashBase<unsigned > >>>int,CryptoPP::HashTransformation>::SetBlockSize(unsigned int) > >>>CryptoPP::IteratedHashBase<unsigned > >>>int,CryptoPP::HashTransformation>::SetStateSize(unsigned int) > >>>CryptoPP::IteratedHashBase<unsigned > >>>int,CryptoPP::HashTransformation>::CreateUpdateSpace(unsigned int&) > >>> > >>>ad nauseum. Its like my app is finding the lib alright, but > >> > >>the lib isnt > >> > >>>exporting correctly? > >>> > >>>-=Bob > >>>(still fighting with the mac) > >>> > >>> > >>> > >> > >> > > > > > > > >
