public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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:55:00 -0000	[thread overview]
Message-ID: <1320918860.13045.95.camel@kare-desktop> (raw)


> Thanx a lot, Marco for takng time!
> 
> 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
> 
> tar xvfz grib_api-1.9.9.tar.gz
> ./configure [--with-jasper=<jasper path>]
> make
> make install
> 
> You then have to edit the makefile.ecmwf_gfortran_32 to have the right
> lib and include path's set for gfortran to find jasper and grib_api. The
> path's found in makefile.ecmwf_gfortran_32 are just showing where the
> programmers installed those lib's before distributing the FLEXPART
> software.
> If you get a successful build, it will still prompt an error since you
> will still miss some expected settings, but you will clearly see whether
> this is a bad binary or not.
> 
> I will definitely try reinstalling an older version of binutils and give
> it a try.
> 
> Thanx again for the advice.
> 
> Regards,
> KÃre
> 
I forgot to say that the file includepar in the FLEXPART folder need to
be edited to look like this in the section:

**********************************************
C Maximum dimensions of the input mother grids
**********************************************

      integer nxmax,nymax,nuvzmax,nwzmax,nzmax,nxshift
      parameter(nxmax=361,nymax=181,nuvzmax=92,nwzmax=92,nzmax=92)
c     parameter(nxmax=361,nymax=181,nuvzmax=61,nwzmax=61,nzmax=61)
c     parameter(nxmax=721,nymax=361,nuvzmax=27,nwzmax=27,nzmax=27)
      parameter(nxshift=359)  ! for ECMWF
c     parameter(nxshift=0)    ! for GFS
      integer nconvlevmax,na 
      parameter (nconvlevmax = nuvzmax-1)
      parameter (na = nconvlevmax+1)



otherwise you will get a crash with some error messages during the make
procedure.

Thanx,
Kåre


             reply	other threads:[~2011-11-10  9:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-10  9:55 Edvardsen Kåre [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-10  9:49 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=1320918860.13045.95.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).