From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15040 invoked by alias); 15 Nov 2011 22:55:28 -0000 Received: (qmail 15032 invoked by uid 22791); 15 Nov 2011 22:55:27 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-ww0-f45.google.com (HELO mail-ww0-f45.google.com) (74.125.82.45) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 15 Nov 2011 22:55:08 +0000 Received: by wwf10 with SMTP id 10so6654847wwf.2 for ; Tue, 15 Nov 2011 14:55:07 -0800 (PST) Received: by 10.180.14.134 with SMTP id p6mr10258464wic.25.1321397707227; Tue, 15 Nov 2011 14:55:07 -0800 (PST) Received: from [192.168.2.99] (cpc2-cmbg8-0-0-cust61.5-4.cable.virginmedia.com. [82.6.108.62]) by mx.google.com with ESMTPS id em10sm829667wib.21.2011.11.15.14.55.03 (version=SSLv3 cipher=OTHER); Tue, 15 Nov 2011 14:55:04 -0800 (PST) Message-ID: <4EC2EDB5.2030704@gmail.com> Date: Tue, 15 Nov 2011 22:55:00 -0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) 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> <4EC2916B.9010400@cs.utoronto.ca> In-Reply-To: <4EC2916B.9010400@cs.utoronto.ca> Content-Type: text/plain; charset=UTF-8 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/msg00257.txt.bz2 On 15/11/2011 16:20, Ryan Johnson wrote: > On 15/11/2011 10:53 AM, Dave Korn wrote: >> On 09/11/2011 12:15, Edvardsen KÃ¥re wrote: >>> In short, the main problem is that I can't build a successful binary >>> from the FLEXPART fortran code >> 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! > Out of curiosity, how then was the OP ever able to make *any* version run? Not clear yet but probably owing to changes in one or more of the array dimensions in the upstream source that he didn't notice taking place. cheers, DaveK -- 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