This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kermode
Recipients kermode
Date 2008-02-10.02:05:42
SpamBayes Score 0.021908127
Marked as misclassified No
Message-id <1202609145.39.0.17652822204.issue2056@psf.upfronthosting.co.za>
In-reply-to
Content
The install command returns the following error when the --compiler
option is provided on the command line:

>python setup.py install --compiler=mingw32
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
   or: setup.py --help [cmd1 cmd2 ...]
   or: setup.py --help-commands
   or: setup.py cmd --help

error: option --compiler not recognized

This is problematic on Windows when MinGW is being used in place of
Visual C. A package can be built with --compiler=mingw32, but if no
compiler is specified for install the following error occurs:

>python setup.py install
running install
running build
running build_py
running build_ext
error: Python was built with Visual Studio 2003;
extensions must be built with a compiler than can generate compatible
binaries.
Visual Studio 2003 was not found on this system. If you have Cygwin
installed,
you can try compiling with MingW32, by passing "-c mingw32" to setup.py.


The work-around is to specify compiler=mingw32 in a setup.cfg file under
a [build] or [build_ext] heading. But this would be inconvenient for
someone who has both Visual C and MinGW and wants to choose.
History
Date User Action Args
2008-02-10 02:05:46kermodesetspambayes_score: 0.0219081 -> 0.021908127
recipients: + kermode
2008-02-10 02:05:45kermodesetspambayes_score: 0.0219081 -> 0.0219081
messageid: <1202609145.39.0.17652822204.issue2056@psf.upfronthosting.co.za>
2008-02-10 02:05:44kermodelinkissue2056 messages
2008-02-10 02:05:43kermodecreate