Windows MinGW binaries now available

[Paul Brook]

On Tuesday 18 January 2005 01:23, Mark Hadfield wrote:
> coudert@lcp.u-psud.fr wrote:
> > For gfortran on mingw, everything is static, so LIBRARY_PATH is indeed
> > the required condition to make it work. The wiki information was updated
> > accordingly (and comp.lang.fortran got the information too).
>
> I've been working away trying to make the "missing crt2.o" problem
> repeatable and made the interesting discovery that it crops up (for me)
> when & only when the working directory is on a different *drive* from
> the Mingw directory (or perhaps from the Gfortran-mingw directory--I
> can't tell as they are both on the same drive, namely D:, on my system).
> That was confusing for a while! Anyway LIBRARY_PATH fixes it (which
> makes the preceding observation somewhat redundant, but I couldn't
> resist sharing it).
>
> Of course this still leaves in the cold those who have not installed
> MinGW and so do not have crt2.o. Would it be sufficient to include a
> copy of this in gfortran-mingw\lib? No. My tests with a minimal program
> show that the following are also needed:
>
>    libmsvcrt.a
>    libmingw32.a
>    libmoldname.a
>    libmingwex.a
>
> Doubtless a more complicated program would need others.

Doesn't mingw provide a convenient package with all the runtime libraries in 
it? I'd suggest including instructions and/or a script to install that.

IIRC you have two options:
- Untar it into ${prefix}/${target}/lib
- Point LIBRARY_PATH at it

Paul