X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.3 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
X-DKIM: Sendmail DKIM Filter v2.8.3 mux1.uit.no pAA9nBRS034235
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: What updates done after October 3 may affect gfortran built binaries?
Date: Thu, 10 Nov 2011 09:49:10 +0000
Message-ID: <1320918505.13045.89.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 pAA9negt020376


> > In order to replicate my build you need to install latest version of the
> > grib_api library
> > (http://www.ecmwf.int/products/data/software/download/grib_api.html)
> > and istall it with jasper
> 
>   What is "jasper"?  Wikipedia lists four entirely different open source
> projects by that name!
> 
>   Also, how big is your build directory?  If of a manageable size, please
> zip/tar it up and send me a copy off-list; if it's huge, please just send me a
> copy of the broken executable (also off-list).
> 
>     cheers,
>       DaveK

Sorry for my lack of info...

jasper is a JPEG 2000 library. It's shipped with cygwin so for
installing grib_api, you just have to specify

./configure prefix=<some-preferred-install-dir> --with-jasper

if you have chosen the jasper package in your cygwin setup. You will
probably experience a hang on

Checking for ANSI C header files...

during ./configure, like I referred to in an earlier thread.
Reinstalling gcc 4.3.4 will solve that for you.

Right now, I'm trying to rebuild my problem code with both earlier
versions of binutils and gcc, like when I could build a working binary.
If it fails, I will send you off-list copies and proper instructions for
a successful build that will give you (probably) a broken binary.

Thanx for your patience,
Kåre