zooko wrote: > Folks: > > I maintain a small library that wraps a few of Crypto++'s algorithms > in Python. The main user it my own tahoe project, but there is at > least one other user. > > Currently I have a problem -- I'm unable to make pycryptopp conform > to the Fedora and Debian packaging standards by linking against the > system-installed libcryptopp.so, because I can't have my own shared > library catch exceptions by type when they were raised from the > separate cryptopp shared library. Full details of the problem are on > this issue tracker ticket and on the tahoe-dev mailing list -- here > is the most recent post on the topic: > > http://allmydata.org/pipermail/tahoe-dev/2009-February/001140.html > > Thanks in advance for any help! > This I believe is your problem. http://gcc.gnu.org/faq.html#dso
I didn't work much with shared libs on linux, so I don't know how to fix that though... --~--~---------~--~----~------------~-------~--~----~ 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. -~----------~----~----~----~------~----~------~--~---
