Your command line is correct, there are a couple of issues that are patched in our version. There is a patch by Fraser Hutchison that fixes this, if you search this list you will find it. All the best David On Sat, Jun 16, 2012 at 12:34 PM, Ben Crowhurst < [email protected]> wrote:
> First of thanks for you time. Secondly sorry for the delay i've been a bit > busy as of late. > > I've taken your comments on board and upgrade by build environment, > however I've found that the error is caused by -stdlib=libc++. If I build > with the following command everything is ok. However I wish to use libc++ > and not stdlibc++. Are you aware of a work around? > > *works* > clang++ -l cryptopp cryptopp_test.cpp -o cryptopp_test -std=c++11 > > *Fails* > clang++ -l cryptopp cryptopp_test.cpp -o cryptopp_test -std=c++11 > -stdlib=libc++ > > > On Monday, 4 June 2012 11:10:11 UTC+1, David Irvine wrote: >> >> Looks like you are trying to use c++0x and an old clang. Either upgrade >> to 3.1 (clang/llvm) or take this flag out. If passing c++11 flag for later >> clang you need -stdlib=libc++ as well in compiler and linker flags. >> >> On Mon, Jun 4, 2012 at 10:58 AM, Ben Crowhurst < >> [email protected]> wrote: >> >>> '-std=c++0x' >> >> >> -- > 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 "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.
