pyopenssl-list

[pyOpenSSL] DLL load failed.

[patrick f. <pa...@we...>]

I was /assuming/ that the import problem was the last of the four 
modules - tsafe - since I could see that the other
3 pyd files were visibly there.  And as I looked for tsafe last Friday, 
I didn't find it.

But as I look more today, yes, tsafe.py/pyc is in place as well.

I seem to be having problems with finding any of these modules (upon 
import that is).  I've tried many variants (of reconfiguring things in 
various ways), but
I keep getting:

L:\MyID\Python\pyOpenSSL\examples>mk_simple_certs.py
Traceback (most recent call last):
  File "L:\pf\Python\pyOpenSSL\examples\mk_simple_certs.py", line 5, in 
<module>

    from OpenSSL import crypto
  File "c:\python26\Lib\site-packages\OpenSSL\__init__.py", line 8, in 
<module>
    import SSL, crypto, rand, tsafe
ImportError: DLL load failed: The specified module could not be found.

L:\MyID\Python\pyOpenSSL\examples>

Needless to say, I've googled the error message - get many hits.  Have 
tried several of the solutions that I thought might be candidates, but
mk_simple_certs.py so far refuses to cooperate.

pat

Re: [pyOpenSSL] DLL load failed.

[Jean-Paul C. <ex...@di...>]

On Mon, 20 Apr 2009 13:39:47 -0700, patrick flaherty <pa...@we...> wrote:
>
>I was /assuming/ that the import problem was the last of the four modules - 
>tsafe - since I could see that the other
>3 pyd files were visibly there.  And as I looked for tsafe last Friday, I 
>didn't find it.
>
>But as I look more today, yes, tsafe.py/pyc is in place as well.
>
>I seem to be having problems with finding any of these modules (upon import 
>that is).  I've tried many variants (of reconfiguring things in various 
>ways), but
>I keep getting:
>
>L:\MyID\Python\pyOpenSSL\examples>mk_simple_certs.py
>Traceback (most recent call last):
>  File "L:\pf\Python\pyOpenSSL\examples\mk_simple_certs.py", line 5, in 
><module>
>
>    from OpenSSL import crypto
>  File "c:\python26\Lib\site-packages\OpenSSL\__init__.py", line 8, in 
><module>
>    import SSL, crypto, rand, tsafe
>ImportError: DLL load failed: The specified module could not be found.

Ah.  This is because of the OpenSSL library not being loadable.  If you
copy ssleay32.a into the Python library directory, C:\python26\Lib\ I
think, then Windows will find it and the error should be resolved.

I hope that the next release of pyOpenSSL will include a Windows installer
which deals with this automatically.

Let me know how it goes,

Jean-Paul

Re: [pyOpenSSL] DLL load failed.

[patrick f. <pa...@we...>]

Hello Jean-Paul,

As you can see below I copied ssleay32.a to c:\python25\Lib, however the 
build (link/ld) fails.

>
> L:\pf\Python\pyOpenSSL>dir c:\python25\lib\ss*.a
>  Volume in drive C has no label.
>  Volume Serial Number is F818-DFCA
>
>  Directory of c:\python25\lib
>
> 03/27/2009  06:32 AM           171,812 ssleay32.a
>                1 File(s)        171,812 bytes
>                0 Dir(s)  103,286,464,512 bytes free
>
> L:\pf\Python\pyOpenSSL>
>
>
> L:\pf\Python\pyOpenSSL>setup.py build_ext -Ic:/openssl32/include -c 
> mingw32
> running build_ext
> building 'OpenSSL.crypto' extension
> writing build\temp.win32-2.5\Release\src\crypto\crypto.def
> x:\pf\cygwin\bin\gcc.exe -mno-cygwin -shared -s 
> build\temp.win32-2.5\Release\src
> \crypto\crypto.o build\temp.win32-2.5\Release\src\crypto\x509.o 
> build\temp.win32
> -2.5\Release\src\crypto\x509name.o 
> build\temp.win32-2.5\Release\src\crypto\pkey.
> o build\temp.win32-2.5\Release\src\crypto\x509store.o 
> build\temp.win32-2.5\Relea
> se\src\crypto\x509req.o 
> build\temp.win32-2.5\Release\src\crypto\x509ext.o build\
> temp.win32-2.5\Release\src\crypto\pkcs7.o 
> build\temp.win32-2.5\Release\src\crypt
> o\pkcs12.o build\temp.win32-2.5\Release\src\crypto\netscape_spki.o 
> build\temp.wi
> n32-2.5\Release\src\util.o c:\Python25\lib\ssleay32.a 
> build\temp.win32-2.5\Relea
> se\src\crypto\crypto.def -LC:\Python25\libs -LC:\Python25\PCBuild 
> -leay32 -lWs2_
> 32 -lpython25 -lmsvcr71 -o build\lib.win32-2.5\OpenSSL\crypto.pyd
> /usr/lib/gcc/i686-pc-mingw32/3.4.4/../../../../i686-pc-mingw32/bin/ld: 
> cannot fi
> nd -leay32
> collect2: ld returned 1 exit status
> error: command 'gcc' failed with exit status 1
>
>
I think the key part might

-leay32

I don't know gcc in detail but my guess is that this statement makes the 
gcc link/ld look for libeay32.dll - not ssleay32.a

pat





Jean-Paul Calderone wrote:
> On Mon, 20 Apr 2009 13:39:47 -0700, patrick flaherty <pa...@we...> wrote:
>   
>> I was /assuming/ that the import problem was the last of the four modules - 
>> tsafe - since I could see that the other
>> 3 pyd files were visibly there.  And as I looked for tsafe last Friday, I 
>> didn't find it.
>>
>> But as I look more today, yes, tsafe.py/pyc is in place as well.
>>
>> I seem to be having problems with finding any of these modules (upon import 
>> that is).  I've tried many variants (of reconfiguring things in various 
>> ways), but
>> I keep getting:
>>
>> L:\MyID\Python\pyOpenSSL\examples>mk_simple_certs.py
>> Traceback (most recent call last):
>>  File "L:\pf\Python\pyOpenSSL\examples\mk_simple_certs.py", line 5, in 
>> <module>
>>
>>    from OpenSSL import crypto
>>  File "c:\python26\Lib\site-packages\OpenSSL\__init__.py", line 8, in 
>> <module>
>>    import SSL, crypto, rand, tsafe
>> ImportError: DLL load failed: The specified module could not be found.
>>     
>
> Ah.  This is because of the OpenSSL library not being loadable.  If you
> copy ssleay32.a into the Python library directory, C:\python26\Lib\ I
> think, then Windows will find it and the error should be resolved.
>
> I hope that the next release of pyOpenSSL will include a Windows installer
> which deals with this automatically.
>
> Let me know how it goes,
>
> Jean-Paul
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and 
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today. 
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> pyopenssl-list mailing list
> pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyopenssl-list
>
>
>   

Re: [pyOpenSSL] DLL load failed.

[Jean-Paul C. <ex...@di...>]

On Thu, 30 Apr 2009 11:37:55 -0700, patrick flaherty <pa...@we...> wrote:
>
>Hello Jean-Paul,
>
>As you can see below I copied ssleay32.a to c:\python25\Lib, however the 
>build (link/ld) fails.
>>
>>L:\pf\Python\pyOpenSSL>dir c:\python25\lib\ss*.a
>>  Volume in drive C has no label.
>>  Volume Serial Number is F818-DFCA
>>
>>  Directory of c:\python25\lib
>>
>>03/27/2009  06:32 AM           171,812 ssleay32.a
>>                1 File(s)        171,812 bytes
>>                0 Dir(s)  103,286,464,512 bytes free
>>
>>L:\pf\Python\pyOpenSSL>
>>
>>
>>L:\pf\Python\pyOpenSSL>setup.py build_ext -Ic:/openssl32/include -c mingw32
>>running build_ext
>>building 'OpenSSL.crypto' extension
>>writing build\temp.win32-2.5\Release\src\crypto\crypto.def
>>x:\pf\cygwin\bin\gcc.exe -mno-cygwin -shared -s 
>>build\temp.win32-2.5\Release\src
>>\crypto\crypto.o build\temp.win32-2.5\Release\src\crypto\x509.o 
>>build\temp.win32
>>-2.5\Release\src\crypto\x509name.o 
>>build\temp.win32-2.5\Release\src\crypto\pkey.
>>o build\temp.win32-2.5\Release\src\crypto\x509store.o 
>>build\temp.win32-2.5\Relea
>>se\src\crypto\x509req.o build\temp.win32-2.5\Release\src\crypto\x509ext.o 
>>build\
>>temp.win32-2.5\Release\src\crypto\pkcs7.o 
>>build\temp.win32-2.5\Release\src\crypt
>>o\pkcs12.o build\temp.win32-2.5\Release\src\crypto\netscape_spki.o 
>>build\temp.wi
>>n32-2.5\Release\src\util.o c:\Python25\lib\ssleay32.a 
>>build\temp.win32-2.5\Relea
>>se\src\crypto\crypto.def -LC:\Python25\libs -LC:\Python25\PCBuild -leay32 
>>-lWs2_
>>32 -lpython25 -lmsvcr71 -o build\lib.win32-2.5\OpenSSL\crypto.pyd
>>/usr/lib/gcc/i686-pc-mingw32/3.4.4/../../../../i686-pc-mingw32/bin/ld: 
>>cannot fi
>>nd -leay32
>>collect2: ld returned 1 exit status
>>error: command 'gcc' failed with exit status 1
>I think the key part might
>
>-leay32
>
>I don't know gcc in detail but my guess is that this statement makes the gcc 
>link/ld look for libeay32.dll - not ssleay32.a
>

It looks like gcc is being told to look in C:\Python25\libs - not C:\Python25\lib.  Perhaps that is causing the trouble?

By the way, with the release of pyOpenSSL 0.9, Windows binary eggs are
available for Python 2.3 and Python 2.5 (Python 2.4 and Python 2.6 are
giving me some problems).  You might want to check out
http://pypi.python.org/pypi/pyOpenSSL/0.9 and see if the pre-built version
works for you.

Jean-Paul