[Python-bugs-list] [ python-Bugs-210683 ] can't compile with SSL support on WinNT (PR#403)
noreply@sourceforge.net
noreply@sourceforge.net
Mon, 06 Aug 2001 14:23:57 -0700
Bugs item #210683, was opened at 2000-07-31 14:14
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=210683&group_id=5470
Category: Windows
Group: Feature Request
Status: Closed
Resolution: Later
Priority: 4
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Moshe Zadka (moshez)
Summary: can't compile with SSL support on WinNT (PR#403)
Initial Comment:
Jitterbug-Id: 403
Submitted-By: falk.lehmann@gmx.net
Date: Mon, 17 Jul 2000 21:59:56 -0400 (EDT)
Version: 1.6a2
OS: WinNT 4.0
I tried to compile Python 1.6a2 on a WinNT box using VC++ 6.00.
The compiler stops with some warnings and an error message:
K:\Projects\Python-1.6a2\Modules\socketmodule.c(2081) : error C2099: initializer
is not a constant
K:\Projects\Python-1.6a2\Modules\socketmodule.c(1947) : warning C4047:
'function' : 'int ' differs in levels of indirection from 'void *'
K:\Projects\Python-1.6a2\Modules\socketmodule.c(1947) : warning C4024: 'memset'
: different types for formal and actual parameter 2
K:\Projects\Python-1.6a2\Modules\socketmodule.c(1948) : warning C4047:
'function' : 'int ' differs in levels of indirection from 'void *'
K:\Projects\Python-1.6a2\Modules\socketmodule.c(1948) : warning C4024: 'memset'
: different types for formal and actual parameter 2
K:\Projects\Python-1.6a2\Modules\socketmodule.c(1933) : warning C4101: 'str' :
unreferenced local variable
K:\Projects\Python-1.6a2\Modules\socketmodule.c(2083) : warning C4047:
'initializing' : 'int ' differs in levels of indirection from 'char [4]'
K:\Projects\Python-1.6a2\Modules\socketmodule.c(2084) : warning C4047:
'initializing' : 'char *' differs in levels of indirection from 'unsigned int '
K:\Projects\Python-1.6a2\Modules\socketmodule.c(2087) : warning C4047:
'initializing' : 'int ' differs in levels of indirection from 'void (__cdecl
*)(struct _object *)'
K:\Projects\Python-1.6a2\Modules\socketmodule.c(2089) : warning C4047:
'initializing' : 'int (__cdecl *)(struct _object *,struct _iobuf *,int )'
differs in levels of indirection from 'struct _object *(__cdecl *)(struct
_object *,char *)'
Thanks in advance for fixing (at least the error).
Falk
====================================================================
Audit trail:
Tue Jul 25 07:25:55 2000 guido changed notes
Tue Jul 25 07:25:55 2000 guido moved from incoming to open
----------------------------------------------------------------------
>Comment By: Tim Peters (tim_one)
Date: 2001-08-06 14:23
Message:
Logged In: YES
user_id=31435
Reassigned to Moshe, cuz he's the last person I recall
making any kind of serious noise about cleaning up the SLL
mess.
Peter, you don't need SSL support to grab URLs on Windows!
It sounds like you're waiting for something you don't
need. socketmodule.c works fine on Windows Python, and has
for years; it's only the SSL *extension* nobody has ported
to Windows.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2001-08-06 12:48
Message:
Logged In: NO
Now that Python 2.1 is out, it sure would be nice
to run Python URL-grabbers on Win systems! The list
o' messages for this item suggests that you'be
been waiting since September 2000 for a volunteer
to fix PR #403, and if I could I would but I can't.
Do the Lords of SourceForge have a guess at the odds
that this will make it into a version of the Win
distribution for Python anytime "soon" (eg, by, say,
Halloween 2001)?
Thanks!
Peter
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2000-09-15 19:07
Message:
Moved to PEP42, awaiting a volunteer can do this.
----------------------------------------------------------------------
Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2000-09-07 15:08
Message:
As we've discussed, this is not an issue for 2.0. Assigned to Tim for resurrection when appropriate since this is Windows-specific.
----------------------------------------------------------------------
Comment By: Jeremy Hylton (jhylton)
Date: 2000-09-07 15:05
Message:
Please do triage on this bug.
----------------------------------------------------------------------
Comment By: Guido van Rossum (gvanrossum)
Date: 2000-08-30 12:01
Message:
Let's not worry about this for 2.0. While the OpenSSL support is part of the socket module, we don't have the resources right now to port that support to Windows.
----------------------------------------------------------------------
Comment By: Jeremy Hylton (jhylton)
Date: 2000-08-23 10:35
Message:
This is a bug. Standard extensions modules should compile, even on obscure platforms like Windows NT. Need a Windows user with time to install OpenSSL to fix this.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2000-08-01 14:02
Message:
Windows compile fails when using openSSL.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2000-08-01 14:02
Message:
From: Guido van Rossum <guido@beopen.com>
Subject: Re: [Python-bugs-list] compiling on WinNT (PR#403)
Date: Mon, 24 Jul 2000 14:00:20 -0500
> sorry, but forgot to write, that I switched on the USE_SSL macro.
> And then the _socket module does not compile.
It appears that the Python SSL code hasn't been ported to Windows.
We'll add this to our TODO list, but it's low priority... Perhaps you
could give it a shot yourself? See www.python.org/patches/ for how to
contribute.
--Guido van Rossum (home page: http://dinsdale.python.org/~guido/)
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2000-08-01 14:02
Message:
From: Falk Lehmann <Falk.Lehmann@gmx.net>
Subject: Re: [Python-bugs-list] compiling on WinNT (PR#403)
Date: Mon, 24 Jul 2000 13:46:45 -0500
[magical fwd by GvR]
Guido,
sorry, but forgot to write, that I switched on the USE_SSL macro.
And then the _socket module does not compile.
Falk
> > I tried to compile Python 1.6a2 on a WinNT box using VC++ 6.00.
>
> Please try the current CVS tree (on its way to 2.0); we have no
> problems compiling this on VC 6.0.
>
> --Guido van Rossum (home page: http://dinsdale.python.org/~guido/)
>
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2000-08-01 14:01
Message:
From: Guido van Rossum <guido@beopen.com>
Subject: Re: [Python-bugs-list] compiling on WinNT (PR#403)
Date: Mon, 24 Jul 2000 11:35:24 -0500
> I tried to compile Python 1.6a2 on a WinNT box using VC++ 6.00.
Please try the current CVS tree (on its way to 2.0); we have no
problems compiling this on VC 6.0.
--Guido van Rossum (home page: http://dinsdale.python.org/~guido/)
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=210683&group_id=5470