Some follow-up. When having a minimal "Path" variable defined (that is with only C:\MinGW\bin), "python setup.py build" does work. There might be something in my complete regular Path that confuses distutils.
2008/5/18 Laurent Gautier <[EMAIL PROTECTED]>: > Hi, > > I am experiencing problems while trying to build a C module. > > I have been through many explanations of how to setup a Windows XP box > and I studied them carefully, and unsuccessfully, before posting here. > > For example, when trying to build the minimal example on wikipedia > http://en.wikibooks.org/wiki/Python_Programming/Extending_with_C#A_minimal_example > > I get: > > C:\Documents and Settings\Bozo\>python setup.py build -g > running build > running build_ext > building 'hello' extension > creating build\temp.win32-2.5\Debug > gcc -mno-cygwin -mdll -O -Wall -g -IC:\Python25\include > -IC:\Python25\PC -c hellomodule.c -o > build\temp.win32-2.5\Debug\hellomodule.o > error: command 'gcc' failed: No such file or directory > > The odd thing is that when I copy/paste the line > gcc -mno-cygwin -mdll -O -Wall -g -IC:\Python25\include > -IC:\Python25\PC -c hellomodule.c -o > build\temp.win32-2.5\Debug\hellomodule.o > into the very same DOS shell that gave the error, that line runs just fine. > > > > Any hint would be greatly appreciated. > > > Thanks, > > > Laurent > _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
