libcrypto++ (Was: NMUs wanted: C++ library packages in need of uploading)
Steve Langasek <vorlon@debian.org> writes:
> Below is a list of libraries which appear to be blocking other packages that
> need to go through the C++ transition[1] and which are themselves ready to
> go through the ABI transition.
[...]
> libcrypto++
I am fighting with libcrypto++ but so far I am loosing.
GCC4 does definitely not like a mix of templates and anonymous enums
[1,2] but there are easy fixes for this.
What is worse, it seems that GCC4 silently refuses to generate code for
some template instantiations, which results in undefined symbols in the
library, as others have experienced [3]. It might however be the case
that GCC4, being more C++ standards compliant, has simply revealed a
problem in the Crypto++ template code.
In any case, the fact is that the non-debian, clean upstream library
code (5.2.1) compiles and links fine with GCC3, but fails to do so with
GCC4. I am still investigating...
--
Jens Peter Secher
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_
[1] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20589
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=318518
[3] http://www.mail-archive.com/cryptopp-list@eskimo.com/msg02236.html
Reply to: