>
> I tried and it didn't work. Using LLVM runtime that's not the only symbol
> not found.
>
> Having say that what was puzzling me most of all was the fact that I have
> another system
> where it was working just fine, I find out that on the new system they
> compiled libcrypto
> using -std=c++11 (apparently)
>
> $ cat /etc/issue
> Ubuntu 14.04.3 LTS \n \l
>
> $ nm /usr/lib/libcryptopp.a | c++filt | grep DEFAULT_CHANNEL
> U CryptoPP::DEFAULT_CHANNEL
>
>
> The other system where it does not work:
>
> $ cat /etc/issue
> Ubuntu Xenial Xerus (development branch) \n \l
>
> $ nm /usr/lib/libcryptopp.a | c++filt | grep DEFAULT_CHANNEL
> U CryptoPP::DEFAULT_CHANNEL[abi:cxx11]
>
> and there we go:
> http://allanmcrae.com/2015/06/the-case-of-gcc-5-1-and-the-two-c-abis/
>
Oh, that was a good find. Sorry about providing the standard sermon.
So I'm clear (and can update the docs): Can the issue be summarized as:
* GCC 5.1 and above
* 5.1 uses a "abi:cxx11" tag in its name mangling
* Clang does not use the "abi:cxx11" tag
Open question: platforms affected? Debian {Testing|Sid}?, Arch?
Open question: does -std=XXX affect it?
I'm thinking the advice of "use the same compiler, options and defines for
both the library and applications" still holds. Can you confirm its OK? Or
can you suggest a change to the text to account for this scenario?
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.
