X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.3 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,NIXSPAM_IXHASH,RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
X-DKIM: Sendmail DKIM Filter v2.8.3 mux2.uit.no pAG95bCS055521
From: =?utf-8?B?RWR2YXJkc2VuIEvDpXJl?= <kare DOT edvardsen AT uit DOT no>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: [SOLVED] Re: What updates done after October 3 may affect gfortran built binaries?
Date: Wed, 16 Nov 2011 09:05:36 +0000
Message-ID: <1321434334.6778.22.camel@kare-desktop>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id pAG967LD028392


>         >    I helped Edvardsen to track this down off-list.  It turns
>         out that FLEXPART
>         > is one of those huge number-crunching Fortran programs
>         that's just jam-packed
>         > with ginormous multi-dimensional arrays.  The final linked
>         executable had 3.38
>         > GB of .bss space!  So, it's not too surprising that it
>         didn't load on 32-bit
>         > Windows; and it's not, as I was worrying, any explicit bug
>         in the compiler or
>         > binutils (although it may be arguable that ld could be
>         helpful if it issued
>         > some kind of warning in these circumstances).
>         Out of curiosity, how then was the OP ever able to make *any*
>         version run?
>         
>         Ryan

I'm not sure of the exact pre-required settings I had when I compiled
FLEXPART to have a successful executable, but there seem to be various
default parameter settings in some of the FLEXPART include files that
will lead to some ginormous multi dimensional arrays. 
I was pretty sure I did the exact same procedure when I compiled
FLEXPART later and got the non working executable, but if the .bss space
was too large, I must have done something else before. It's just that I
can't possibly think of anything I did different.
However, I'm determined to locate the problem, to advice the FLEXPART
developers. I don't want others to go through something similar.

Kåre