Problem compiling NONMEM with mingw gfortran 4.3.0 builds

[FX Coudert]

>>> or gfortran 4.1.2?
>>>
>> That would work, but I would recommend to use 4.2.x, which has many
>> Fortran improvements, is a stable version and already used as system
>> compiler of some Linux distributions.
>>
>> As I don't have a working Windows, someone else has to build gfortran
>> 4.2.x/Mingw ... FX?

I would also strongly recommend 4.2.x over 4.1.x. Especially for  
MinGW, as I don't remember if 4.1 was fully functional.

As for who might be building binaries, I don't intend to provide  
4.2.x binaries for MinGW; the whole goal of making binaries available  
by the gfortran community is to help people taste the latest,  
including bugs. In the "natural order of things", It's up to the  
vendor of each system to build and package GCC for you, if you're  
just a regular user. I do think the MinGW project intends to actually  
release GCC-4.2 binaries, or so Danny Smith said a few months back.  
Danny, any fresh news on that?

> We could use official or semi-official builds of stable releases  
> for production, especially if those releases were well-known and  
> used by many users. I actually tried DJGPP builds of gfortran  
> first, but ran into the 127 character command line limit. One of my  
> problems with MinGW builds is that there are so few pre-built  
> binaries for Windows, and they don't seem to be very well known. I  
> think the MinGW could benefit users by providing pre-built binaries  
> as DJGPP does, and those users could in turn help MinGW by  
> providing more extensive testing of the releases.

I don't quite understand what you mean here. MinGW (the project) has  
many binaries available for download, and they actually are quite  
conservative with respect to the software they package, I think. So,  
they do have well-known, stable binaries in my opinion. In fact,  
they're actually to stable for you to use, right now!

FX