Message-ID: <4EC2916B.9010400@cs.utoronto.ca>
Date: Tue, 15 Nov 2011 11:20:59 -0500
From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: [SOLVED] Re: What updates done after October 3 may affect gfortran built binaries?
References: <1320840871.13045.51.camel@kare-desktop> <4EC28AE7.70600@gmail.com>
In-Reply-To: <4EC28AE7.70600@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 15/11/2011 10:53 AM, Dave Korn wrote:
> On 09/11/2011 12:15, Edvardsen Kåre wrote:
>> This is again related to the failure of execution of a gfortran built
>> binary ("cannot execute binary", see thread
>> http://cygwin.com/ml/cygwin/2011-11/msg00034.html )
>>
>> In short, the main problem is that I can't build a successful binary
>> from the FLEXPART fortran code
>
>    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


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple