From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5034 invoked by alias); 15 Nov 2011 16:21:49 -0000 Received: (qmail 5019 invoked by uid 22791); 15 Nov 2011 16:21:45 -0000 X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Received: from smtp0.epfl.ch (HELO smtp0.epfl.ch) (128.178.224.219) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Tue, 15 Nov 2011 16:21:05 +0000 Received: (qmail 373 invoked by uid 107); 15 Nov 2011 16:21:01 -0000 Received: from sb-gw13.cs.toronto.edu (HELO discarded) (128.100.3.13) (authenticated) by smtp0.epfl.ch (AngelmatoPhylax SMTP proxy) with ESMTPA; Tue, 15 Nov 2011 17:21:01 +0100 Message-ID: <4EC2916B.9010400@cs.utoronto.ca> Date: Tue, 15 Nov 2011 16:21:00 -0000 From: Ryan Johnson 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 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-11/txt/msg00244.txt.bz2 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