From: "Edvardsen Kåre" <kare.edvardsen@uit.no>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: What updates done after October 3 may affect gfortran built binaries?
Date: Thu, 10 Nov 2011 09:49:00 -0000 [thread overview]
Message-ID: <1320918505.13045.89.camel@kare-desktop> (raw)
> > 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
next reply other threads:[~2011-11-10 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 9:49 Edvardsen Kåre [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-10 9:55 Edvardsen Kåre
2011-11-09 13:32 Edvardsen Kåre
2011-11-10 5:24 ` Dave Korn
2011-11-09 12:15 Edvardsen Kåre
2011-11-09 13:07 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1320918505.13045.89.camel@kare-desktop \
--to=kare.edvardsen@uit.no \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).