#44: test what happens if another Python module loads Crypto++ dynamic link
library
------------------------+---------------------------------------------------
Reporter: zooko | Owner:
Type: defect | Status: new
Priority: major | Version: 0.5.19
Resolution: | Keywords:
Launchpad Bug: |
------------------------+---------------------------------------------------
Comment (by zooko):
Hm, so as usual actually sitting down and trying to write a unit test
makes me realize that I don't really understand.
Along the way of attempting to understand, I re-read this thread:
http://groups.google.com/group/cryptopp-
users/browse_thread/thread/eb815f228db50380
and then I found this nice page about visibility control in GCC:
http://www.nedprod.com/programs/gccvisibility.html
Now I think the way to test this is to make another .so aside from
_pycryptopp.so which also links to libcryptopp.so and then load
_pycryptopp.so and then load that other .so.
--
Ticket URL: <http://allmydata.org/trac/pycryptopp/ticket/44#comment:3>
pycryptopp <http://allmydata.org/trac/pycryptopp>
Python bindings for the Crypto++ library
_______________________________________________
tahoe-dev mailing list
[email protected]
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
