pyopenssl-list

[pyOpenSSL] Trying to build pyOpenSSL on windows (mingw vs MS compiler).

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

Hi,

Whether I use a cmd window (DOS) or a cygwin bash shell, I seem in both 
cases to get the MS compiler.

This compiles the first two modules:  crypto.obj and x509.obj.  But  it 
(the MS compiler [VS 2008]) chokes on x509name.c
with

x509name.c(16): error C2133: 'crypto_X509Name_methods' : unknown size.

My guess is that what I need that I need to be using mingw instead of 
the MS compiler.

But what I can't figure out is how to get setup.py to _use_ mingw 
instead of the VS 2008 compiler?

thanx - pat

[pyOpenSSL] Trying to build pyOpenSSL on windows (mingw vs MS compiler).

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

OK - I've got it build and installed.

The library you need (and that I didn't have) is: ssleay32.a.  There's a 
MINGW subdirectory in the 32-bit
version of the OpenSSL kit here:

http://www.slproweb.com/products/Win32OpenSSL.html

_But the same library_ is not to be found in the 64 bit version.  I have 
a 64-bit machine and so first downloaded
the 64 bit version.  Eventually tried downloading the 32 bit version and 
found what I needed.

You put this into c:\pythonXX\libs.  The current setup.py expects this 
in c:\python25, but I have 2.6 so I needed
to modify the reference in setup.py appropriately.

build_ext then fully works and makes three .pyd files (dynamically 
loadable python modules/libraries I believe).

python setup.py build   (without the ext) then works.

And python install also works.

So then I turned my attention to the example programs.  I try to run the 
one to make the certificates and it crashes
upon startup because it can't import module tsafe.  tsafe = thread safe.

So where do I find this?  Am again looking around the web, but, so far, 
no joy.

pat

Re: [pyOpenSSL] Trying to build pyOpenSSL on windows (mingw vs MS compiler).

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

On Fri, 17 Apr 2009 16:53:54 -0700, patrick flaherty <pa...@we...> wrote:
>
>OK - I've got it build and installed.

Hooray.

> [snip]
>
>_But the same library_ is not to be found in the 64 bit version.  I have a 
>64-bit machine and so first downloaded
>the 64 bit version.  Eventually tried downloading the 32 bit version and 
>found what I needed.
>
>You put this into c:\pythonXX\libs.  The current setup.py expects this in 
>c:\python25, but I have 2.6 so I needed
>to modify the reference in setup.py appropriately.

I haven't done any testing of pyOpenSSL on 64 bit Windows.  So maybe this
works, but I have no idea. :)

> [snip]
>So then I turned my attention to the example programs.  I try to run the one 
>to make the certificates and it crashes
>upon startup because it can't import module tsafe.  tsafe = thread safe.
>
>So where do I find this?  Am again looking around the web, but, so far, no 
>joy.

What do you mean "it crashes"?  Do you have the tsafe module?  It should
have been installed with the rest of pyOpenSSL.

Jean-Paul

Re: [pyOpenSSL] Trying to build pyOpenSSL on windows (mingw vs MS compiler).

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

Use the web - right?

This compiled all the modules (but with a number of warnings):

(from a cmd window)   setup.py build_ext -I c:\openssl\include -c mingw32

But then the gcc ( gcc -mno-cygwin ) link failed with:

gcc: c:\python25\libs\ssleay32.a: No such file or directory.

Actually I'd looked around the web already for ssleay32.a and found lots 
of references but didn't seem to find the library as such?

Sorry for all the fumbling around.

pat



patrick flaherty wrote:
> Hi,
>
> Whether I use a cmd window (DOS) or a cygwin bash shell, I seem in 
> both cases to get the MS compiler.
>
> This compiles the first two modules:  crypto.obj and x509.obj.  But  
> it (the MS compiler [VS 2008]) chokes on x509name.c
> with
>
> x509name.c(16): error C2133: 'crypto_X509Name_methods' : unknown size.
>
> My guess is that what I need that I need to be using mingw instead of 
> the MS compiler.
>
> But what I can't figure out is how to get setup.py to _use_ mingw 
> instead of the VS 2008 compiler?
>
> thanx - pat
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> 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] Trying to build pyOpenSSL on windows (mingw vs MS compiler).

[William H. <wg...@gm...>]

I would love to know the answer to this too.  Keep it up!

On Fri, Apr 17, 2009 at 12:00 PM, patrick flaherty <pa...@we...> wrote:

>
> Use the web - right?
>
> This compiled all the modules (but with a number of warnings):
>
> (from a cmd window)   setup.py build_ext -I c:\openssl\include -c mingw32
>
> But then the gcc ( gcc -mno-cygwin ) link failed with:
>
> gcc: c:\python25\libs\ssleay32.a: No such file or directory.
>
> Actually I'd looked around the web already for ssleay32.a and found lots of
> references but didn't seem to find the library as such?
>
> Sorry for all the fumbling around.
>
> pat
>
>
>
> patrick flaherty wrote:
>
> Hi,
>
> Whether I use a cmd window (DOS) or a cygwin bash shell, I seem in both
> cases to get the MS compiler.
>
> This compiles the first two modules:  crypto.obj and x509.obj.  But  it
> (the MS compiler [VS 2008]) chokes on x509name.c
> with
>
> x509name.c(16): error C2133: 'crypto_X509Name_methods' : unknown size.
>
> My guess is that what I need that I need to be using mingw instead of the
> MS compiler.
>
> But what I can't figure out is how to get setup.py to *use* mingw instead
> of the VS 2008 compiler?
>
> thanx - pat
>
> ------------------------------
> ------------------------------------------------------------------------------
> 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 lis...@li...https://lists.sourceforge.net/lists/listinfo/pyopenssl-list
>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>