Mikhail Gusarov <dotted...@dottedmag.net> writes:
> Hello,
>
> I was packaging 1.0 for Debian and found out that there are private
> symbols exported by the library:
>
> + _libssh2_cipher_crypt
> + _libssh2_cipher_init
> + _libssh2_dsa_new
> + _libssh2_dsa_new_private
> + _libssh2_dsa_sha1_sign
> + _libssh2_dsa_sha1_verify
> + _libssh2_pem_decode_integer
> + _libssh2_pem_decode_sequence
> + _libssh2_pem_parse
> + _libssh2_rsa_new
> + _libssh2_rsa_new_private
> + _libssh2_rsa_sha1_sign
> + _libssh2_rsa_sha1_verify
> + _libssh2_session_set_blocking
>
> Shouldn't they be hidden in the library?
I believe so. I propose to use the following patch which makes libtool
hide the other symbols. We should also bump the revision field of the
ABI version before we make the next release, to avoid file name
collisions.
/Simon
--- Makefile.am.~1.13.~ 2008-11-21 15:34:03.000000000 +0100
+++ Makefile.am 2009-02-16 22:28:23.000000000 +0100
@@ -51,4 +51,5 @@
#
libssh2_la_LDFLAGS = $(VERSION) -no-undefined \
+ -export-symbols-regex '^libssh2_.*' \
$(LTLIBGCRYPT) $(LTLIBSSL) $(LTLIBZ)
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
libssh2-devel mailing list
libssh2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libssh2-devel
