[ Subject changed, and OT tagged because this is really becoming about windows
command shell programming techniques. ]
Joe Pham wrote:
> Dave Korn writes:
>
>> What about calling distutils.Ccompiler.set_executables() in your
>> script that invokes distutils?
>
> I probably could, but I'd have
Dave Korn writes:
> What about calling distutils.Ccompiler.set_executables() in your
>script that invokes distutils?
I probably could, but I'd have to do that for each and every package that I
need to build.
-Joe Pham
You can tak
Joe Pham wrote:
>> Can you just tell windows python to use "gcc-3" in distutils instead
>> of "gcc", and not have to munge your cygwin installation?
>
> Not through any command line parameters. I'd have to change the distutils
> source.
What about calling distutils.Ccompiler.set_executables(
>Can you just tell windows python to use "gcc-3" in distutils instead
>of "gcc", and not have to munge your cygwin installation?
Not through any command line parameters. I'd have to change the distutils
source.
-Joe Pham
Click her
Joe Pham wrote:
> Using non-cygwin python-2.5.4
^^
> Apparently, distutils failed to locate the full path to gcc.exe
> because /bin/gcc.exe is an s-link instead of a regular file
Non-cygwin applications of course do not recognise nor follow Cygwin symlinks.
> (os.path.isfile()
Using non-cygwin python-2.5.4, distutils failed to compile c files and
generated the following error message:
error: command 'gcc' failed: No such file or directory
Apparently, distutils failed to locate the full path to gcc.exe because
/bin/gcc.exe is an s-link instead of a regular file (os.pa
6 matches
Mail list logo
