On Mon, Nov 21, 2016 at 4:45 PM, <[email protected]> wrote: > Sorry about not replying to the last response, but am still having this > issue even after removing the -fembed-bitcode. I have included the output > of the errors below. I am unfortunately stuck with iOS 10 and cannot use an > older version due to a different library. Any help or an idea of where to > look would be much appreciated. CryptoPP was built in arm64 so it is indeed > the right architecture. I can add the output of the build if it is needed > but it did build without any issues. > > "CryptoPP::Filter::TransferTo2(CryptoPP::BufferedTransformation&, unsigned > long long&, std::__1::basic_string<char, std::__1::char_traits<char>, > std::__1::allocator<char> > const&, bool)", referenced from: > vtable for CryptoPP::StringSource in libA.a(ClassA.o) > vtable for CryptoPP::SourceTemplate<CryptoPP::StringStore> in > libA.a(ClassA.o) > "CryptoPP::Filter::CopyRangeTo2(CryptoPP::BufferedTransformation&, > unsigned long long&, unsigned long long, std::__1::basic_string<char, > std::__1::char_traits<char>, std::__1::allocator<char> > const&, bool) > const", referenced from: > vtable for CryptoPP::StringSource in libA.a(ClassA.o) > vtable for CryptoPP::SourceTemplate<CryptoPP::StringStore> in > libA.a(ClassA.o) > "CryptoPP::BufferedTransformation::Skip(unsigned long long)", referenced > from: > vtable for CryptoPP::StringSource in libA.a(ClassA.o) > vtable for CryptoPP::SourceTemplate<CryptoPP::StringStore> in > libA.a(ClassA.o) > "CryptoPP::StringStore::TransferTo2(CryptoPP::BufferedTransformation&, > unsigned long long&, std::__1::basic_string<char, > std::__1::char_traits<char>, std::__1::allocator<char> > const&, bool)", > referenced from: > CryptoPP::SourceTemplate<CryptoPP::StringStore>::Pump2(unsigned long > long&, bool) in libA.a(ClassA.o) > > ld: symbol(s) not found for architecture arm64 > clang: error: linker command failed with exit code 1 (use -v to see > invocation)
What version of the library? Are you using Master, a ZIP, or something else? Is the other library shipping/using Crypto++ also? The missing "unsigned long long" could indicate this issue detailed for the distros, like Debian and Fedora: https://www.cryptopp.com/release565.html . However, since you are building it yourself, it should not be a problem. Jeff -- -- 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.
