I have been doing regular builds of my software that uses crypto++ for a 
while now. Today I did a build, then accidentally pulled to the latest head 
of crypto, and now my software doesn't compile.
It says:

Undefined symbols for architecture armv7:

"vtable for CryptoPP::Base64Decoder", referenced from ...

ld: symbol(s) not found for architecture armv7


$ lipo -info  libcryptopp-ios.a

Architectures in the fat file: libcryptopp-ios.a are: armv7 armv7s x86_64 
arm64


$ nm libcryptopp-ios.a  | grep Base64Decoder

warning: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/nm:
 
no name list

0000000000000624 T __ZN8CryptoPP13Base64Decoder22GetDecodingLookupArrayEv

0000000000027530 b 
__ZZN8CryptoPP13Base64Decoder22GetDecodingLookupArrayEvE13s_initialized

0000000000027540 b 
__ZZN8CryptoPP13Base64Decoder22GetDecodingLookupArrayEvE7s_array


$ nm libcryptopp-ios.a  | grep Base64Encoder

0000000000000000 T 
__ZN8CryptoPP13Base64Encoder18IsolatedInitializeERKNS_14NameValuePairsE

0000000000020632 S __ZN8CryptoPP13Base64EncoderD0Ev

00000000000204be S __ZN8CryptoPP13Base64EncoderD1Ev

0000000000021e50 S __ZTIN8CryptoPP13Base64EncoderE

0000000000021bf0 S __ZTSN8CryptoPP13Base64EncoderE

0000000000021c30 S __ZTVN8CryptoPP13Base64EncoderE

000000000002096e S __ZThn8_N8CryptoPP13Base64EncoderD0Ev

00000000000207fa S __ZThn8_N8CryptoPP13Base64EncoderD1Ev


I have not touched the library (It still has my Jan 13 compile date) or the 
code that calls the crypto functions, but now with the simple update of 
source it fails to compile.


Any idea why this may be?

-- 
-- 
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