re-post: did send it Bill only, sorry.
Am Montag 19 Mai 2008 00:29:43 schrieb Bill Hoffman:
> Perhaps it is better to use a make that does not do this. mingw-make,
> cygwin make, native win32 gmake. I am not sure you can completely avoid
> / type arguments in the entire tool chain for windows.
>
Maik Beckmann wrote:
Am Sonntag 18 Mai 2008 22:35:53 schrieb Stefan Buschmann:
Hi,
I don't know ifort, but I had the same problem with Makefiles and MSYS a
while ago.
Since it works with cygwin I assume ifort knows cygwin and handles the
forward slash right. Does anyone know if ifort has a f
Am Sonntag 18 Mai 2008 22:35:53 schrieb Stefan Buschmann:
> Hi,
>
> I don't know ifort, but I had the same problem with Makefiles and MSYS a
> while ago.
>
> > Since it works with cygwin I assume ifort knows cygwin and handles the
> > forward slash right. Does anyone know if ifort has a flag or en
Hi,
I don't know ifort, but I had the same problem with Makefiles and MSYS a
while ago.
Since it works with cygwin I assume ifort knows cygwin and handles the forward
slash right. Does anyone know if ifort has a flag or environment variable
name to set which tells ifort its working on windo
Hello List,
Today I found the reason why the MSYS generator fails with ifort.
This line
ifort -fpp test.f
works at the standard cmd, the cygwin shell and msys shell. But this one
ifort /fpp test.f
fails when doing it in msys, because /fpp is considered as an file and ifort
wants to com
