Win2k and mingw gnu compiler with Python 2.3.2?

[dbrown2 at yahoo.com]

John,

Still no luck.  When I run "build" I do use the compiler flag as
shown:

C:>python setup.py build --compiler=mingw32
C:>running build
C:>running build_py
C:>running build_ext
C:>

This seems to work fine.  The "install" command will not accept a
compiler option.   Thanks for the suggestion though.

The error 
     "Python was built with version 6 of Visual Studio, and extensions
     need to be built with the same version of the compiler, but it
     isn't installed."

appears to be a windows issue related to the compiler used to build
the binary installer version.  I could not find mention at python.org
of who actually produces the windows installer and also couldn't find
a credit in the installer itself.  Could someone point me to an
appropriate contact or email to report this?  It doesn't appear to be
a python language issue.

-- David



jjl at pobox.com (John J. Lee) wrote in message news:<874qy0by65.fsf at pobox.com>...
> dbrown2 at yahoo.com writes:
> 
> > I'm trying to understand and document how to install pypar on Win2k.
> > Pypar needs to be installed with some MPI library code and also needs
> > libpython23.a and other files which are not included with the python
> > Windows binary installation.  I've got that worked out but still no
> > success.
> 
> It's a pain, isn't it?
> 
> 
> > Here's the error message I'm seeing:
> > 
> > >python setup.py install
>  [...]
> > >error: Python was built with version 6 of Visual Studio, and
>  extensions need to
> > >be built with the same version of the compiler, but it isn't
> > installed.
> > 
> > I also get the error if I use gcc directly.  I'm trying to use the
> > mingw version of the gnu compiler in a command window (not cygwin).  I
> 
> Something like
> 
> python setup.py install -cmingw32
> 
> 
> ?  But if that is the problem, dunno why you were getting away with it
> on 2.2.
> 
> 
> John