pyOpenSSL

build failure on Fedora 14 -- missing symlink for libcrypto.so.1.0.0 ? Fixed by clean and rebuild?

Bug #909608 reported by Zooko Wilcox-O'Hearn
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Tahoe-LAFS
Unknown
Unknown
pyOpenSSL
New
Undecided
Unassigned

Bug Description

A Tahoe-LAFS user reported that pyOpenSSL 0.13 on Fedora 14 with Python 2.7 failed on import with ImportError 'libcrypto.so.1.0.0: cannot open shared object file: No such file or directory'. Apparently there was a missing symlink so that the pyOpenSSL .so was looking for "libcrypto.so.1.0.0" but the only file present was named "libcrypto.so". Also apparently removing the pyOpenSSL installation entirely and rebuilding it fixed the problem!

There is a transcript of the original reporter, tcatm, reporting this at https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1635

Revision history for this message
Jean-Paul Calderone (exarkun) wrote :

The transcript lacks a description of how pyOpenSSL was actually installed the first time.

Revision history for this message
Daira Hopwood (daira) wrote :

It was strictly speaking not installed; it was built as a dependency of Tahoe-LAFS. That involves a recursive invocation of, essentially, 'python setup.py build' with the option '--prefix=support'. The version of easy_install is the one provided by the zetuptoolz fork of setuptools that is bundled with Tahoe-LAFS.

I suspect that these details aren't actually relevant to the bug and that it can be reproduced with pycryptopp alone using 'setup.py build', but I could be wrong.

Revision history for this message
Daira Hopwood (daira) wrote :

s/pycryptopp alone/pyOpenSSL alone/

Revision history for this message
Jean-Paul Calderone (exarkun) wrote :

Alright. It sounds like the next step would be to verify that the problem really does occur on Fedora 14 when doing just "setup.py build". I do not have a Fedora 14 machine around. I can probably find a VM or something eventually, but it will likely be quite a while before I have time for this. If anyone else wants to perform this investigation, it might speed things up.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.