[Python-bugs-list] [Bug #110683] compiling on WinNT (PR#403)

[noreply@sourceforge.net]

Bug #110683, was updated on 2000-Jul-31 21:14
Here is a current snapshot of the bug.

Project: Python
Category: Windows
Status: Open
Resolution: None
Bug Group: None
Priority: 6
Summary: compiling on WinNT (PR#403)

Details: 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

Follow-Ups:

Date: 2000-Aug-01 21:01
By: none

Comment:
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/)


-------------------------------------------------------

Date: 2000-Aug-01 21:02
By: none

Comment:
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/)
> 


-------------------------------------------------------

Date: 2000-Aug-01 21:02
By: none

Comment:
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/)


-------------------------------------------------------

Date: 2000-Aug-01 21:02
By: none

Comment:
Windows compile fails when using openSSL.
-------------------------------------------------------

Date: 2000-Aug-23 17:35
By: jhylton

Comment:
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.

-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=110683&group_id=5470