Re: [f2py] -mno-cygwin
Pearu Peterson <[email protected]> Fri, 15 Oct 2010 21:11:32 +0300
| Newsgroups | gmane.comp.python.f2py.user |
|---|---|
| Message-ID | <[email protected]> |
Hi, Could you try removing all -mno-cygwin occurrences from the following files: numpy/distutils/mingw32ccompiler.py numpy/distutils/fcompiler/gnu.py to see if this fixes compilations. Let me know if you got it working and what changes were needed in these files. Then I can prepare the corresponding patch for numpy.distutils.. HTH, Pearu On Fri, Oct 15, 2010 at 6:37 PM, Steve Westenbroek <[email protected]> wrote: > Greetings, > > I recently upgraded my compiler to gcc/gfortran version 4.6.0 20101009, > running under MSYS/MinGW. > > Before the upgrade, f2py happily compiled my fortran code into a Python > module. Following the upgrade, f2py fails with the following message: > > Found executable C:\MinGW\bin\gcc.exe > cc1.exe: error: unrecognized command line option '-mno-cygwin' > error: Command "gcc -mno-cygwin -O2 -Wall -Wstrict-prototypes [snip]" > failed with exit status 1 > > Given that the "-mno-cygwin" flag is apparently obsolete (and redundant > under MinGW), how can I force f2py to stop tacking it on when attempting > to compile a module? > > Thanks, > > - Steve > > _______________________________________________ > f2py-users mailing list > f2py-users-Y4l6ocDipWCuvFJfX82//[email protected] > http://cens.ioc.ee/mailman/listinfo/f2py-users >