Hi Yong,

I got stuck on these two linking errors. I post the whole message as 
follows.

Undefined symbols for architecture i386:
>   "_clock$UNIX2003", referenced from:
>       CryptoPP::X917RNG::X917RNG(CryptoPP::BlockTransformation*, unsigned 
> char const*, unsigned char const*) in libcryptopp-osx.a(rng.o)
>       
> CryptoPP::X917RNG::GenerateIntoBufferedTransformation(CryptoPP::BufferedTransformation&,
>  
> std::__1::basic_string<char, std::__1::char_traits<char>, 
> std::__1::allocator<char> > const&, unsigned long long) in 
> libcryptopp-osx.a(rng.o)
>   "_sleep$UNIX2003", referenced from:
>       CryptoPP::BlockingRng::GenerateBlock(unsigned char*, unsigned long) 
> in libcryptopp-osx.a(osrng.o)
> ld: symbol(s) not found for architecture i386
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)


I've built cryptopp as a dynamic library (.a) separately for iOS device, 
and simulator.
I can successfully build the project with cryptopp and run on iOS device, 
but not for simulator in which it shows the error above.

Do I miss anything?

Wasin

On Sunday, October 13, 2013 1:59:53 PM UTC+7, Yong Duk Lee wrote:
>
>
> Hello.
>
>
> I am using the cryptopp library from cryptopp-5.6.2-ios-7.0 in Xcode 5.0.
>
> Everything works fine, and I can run my program either in simulator or 
> device.
>
> However, when I try to archive the program in xcode to build ad-hoc app, 
> it 
>
> says "Undefined symbols for architecture arm64".
>
>
> The library was said to be built for arm7, arm7s, arm64, i386. 
>
>
> What could be wrong? Can anyone help? 
>
>
> Thank you.
>
>
>
>
>
>

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