Hello everyone,

I am pleased to see that the 12.5 compiler fixes the 12.4 compiler bug that 
was nobbling me earlier. The test harness and benchmark work ok. However I 
must be building the library wrong because although cryptopp builds ok, I 
cannot get my product to build that uses it. All the references to the 
crypto library remain unsatisfied. The linker says that the symbols I am 
referencing cannot be found yet when I use nm -C I see that they are there.

I had a similar problem with another third pary library that I use and the 
problem was eventually tracked down to the inconsistent use of the 
-std=c++14 option. I need to use this option because I am using Rogue Wave 
foundation libraries (please don't laugh) and the RW build requires it. I 
compile all the C++ code in project, including the source of all third 
party libraries, with the same compiler options. This means that the 
cryptopp build requires -std=c++14 also. So I spent some time trying to 
make sure that I am indeed using the same set of compiler options 
throughout. But no luck. Is anyone in a position to help me please? This 
problem only occurs on SPARC solaris. The issue does not apply to Intel 
Solaris. And it only applies to version 12.5 of the sun compiler. The 
compiler options I am using are: -D_REENTRANT  -mt -m64 -xbuiltin=%all 
-xlibmil -errtags -xldscope=global -erroff -PIC -std=c++14


-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
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 cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to