From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23637 invoked by alias); 9 Nov 2011 13:07:13 -0000 Received: (qmail 23629 invoked by uid 22791); 9 Nov 2011 13:07:12 -0000 X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 tests=AWL,BAYES_50,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_BJ,TW_YG X-Spam-Check-By: sourceware.org Received: from mail-wy0-f171.google.com (HELO mail-wy0-f171.google.com) (74.125.82.171) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 09 Nov 2011 13:06:46 +0000 Received: by wyh11 with SMTP id 11so1942575wyh.2 for ; Wed, 09 Nov 2011 05:06:45 -0800 (PST) Received: by 10.227.206.146 with SMTP id fu18mr1756849wbb.7.1320844005116; Wed, 09 Nov 2011 05:06:45 -0800 (PST) Received: from [172.21.193.102] (85-18-126-22.ip.fastwebnet.it. [85.18.126.22]) by mx.google.com with ESMTPS id fy13sm5572122wbb.18.2011.11.09.05.06.43 (version=SSLv3 cipher=OTHER); Wed, 09 Nov 2011 05:06:44 -0800 (PST) Message-ID: <4EBA7AE3.8020108@gmail.com> Date: Wed, 09 Nov 2011 13:07:00 -0000 From: Marco Atzeri User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: What updates done after October 3 may affect gfortran built binaries? References: <1320840871.13045.51.camel@kare-desktop> In-Reply-To: <1320840871.13045.51.camel@kare-desktop> 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/msg00137.txt.bz2 On 11/9/2011 1:15 PM, 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 (just google "FLEXPART nilu" if you are > curious of what FLEXPART is) on a cygwin installation I did just over a > week ago, but it builds and run without problem on an installation from > October 3. I get no differences in warnings from the bad build compared > to the good one, so I really don't know what to look for. > > So far I have come to the conclusion that this must be related to one or > several changes in the cygwin distribution done after October 3. Through > try and failure testing I found that this is not affected by > gfortran/gcc as both gcc 4.3.4 and gcc 4.5.3 works. The latter hangs on > '$EGREP' calls in the 'grib_api' (required library) configure script, > but the workaround of changing to 'egrep' works fine. > > I have posted the output from strace, objdump and cygcheck for some of > you to look at in the former thread, but it seem like this is far from a > straight forward problem. > > I can see from the [ANNOUNCEMENT] posts that a few things in this cygwin > distro have been updated since October 3 and I kindly ask if someone > have an idea of what updates since then may cause a badly gfortran built > binary if it has nothing to do with gcc alone? > > I will now start going through the updates and change back to versions > yielding October 3 if possible. I think this is important since cygwin > will give the opportunity to run and develop FLEXPART on Windows > machines the way linux-users are used to. In addition, I also see a > potential problem of other fortran software that people want to run > under cygwin. > > Regards, > KÃ¥re my guess binutils http://cygwin.com/ml/cygwin-announce/2011-10/msg00028.html or some BLODA. I downloaded the http://zardoz.nilu.no/~flexpart/flexpart/flexpart_82-3.tar.gz but it is not clear to me how to replicate your build. make -f makefile.gfs_gfortran_32 fails here: --------------------------------------------------------------- $ make -f makefile.gfs_gfortran_32 gfortran -O2 -m32 -fconvert=little-endian -frecord-marker=4 -I/nilu2/home/flexpart/lib/gfortran/include -c -o writeheader.o writeheader.f includecom:685.22: Included at writeheader.f:50: common /globalr/ ! REAL 1 Error: The equivalence set for 'pplev' cause an invalid extension to COMMON 'globalr' at (1) ...... --------------------------------------------------------------- Regards Marco -- 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