[Mingw-msys] Re: Msys and Fortran 90

[Dominique O. <dom...@gm...>]

> Date: Mon, 21 Feb 2005 07:37:31 -0500 (EST)
> Subject: Re: [Mingw-msys] Msys and Fortran 90
> From: "Earnie Boyd" <ea...@us...>
> To: min...@li...
> Reply-To: min...@li...

> >> 2. Is it possible to use g95 from within MinGW/MSYS?

> PATH=/path/to/g95/bin:$PATH /path/to/g95/bin/g95 ...

Great! It was so simple, my question was stupid. Sorry and thanks!

> To: min...@li...
> From: Mark Hadfield <m.h...@ni...>
> Date: Tue, 22 Feb 2005 16:11:39 +1300
> Subject: [Mingw-msys] Re: Msys and Fortran 90
> Reply-To: min...@li...

> Writing a shell script to serve in place of DFVARS.BAT is not that hard.

Sure, thanks a lot for the script. I realize it isn't hard to rewrite
one, but i guess i just like to have the conversion process more or
less automated, so other users don't have to rely on my own conversion
of the batch file. I was just noting that gotos and labels make the
automation harder.

Regarding my other qestion on the -I flag and the form of the path
(windows style vs. unix style), i realize it might not be the goal of
MinGW/Msys to be a full port of Unix/Linux to Windows, but i note the
following: from an msys command line, calling

     g95 -I/a/b/c/d

works fine, but calling

     f90 -I/a/b/c/d

doesn't (where f90 is the Digital Fortran). Instead it wants me to say

     f90 -Ia:\b\c\d

Why is that? Why do some windows program accept the msys path and
others don't? How do i work around that?

Thanks a lot,
Dominique