From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Incorrect module file format in Fortran netCDF package
Date: Fri, 04 Oct 2013 09:57:00 -0000 [thread overview]
Message-ID: <524E90E4.80207@gmail.com> (raw)
In-Reply-To: <524E82DC.6080103@gmail.com>
Il 10/4/2013 10:57 AM, marco atzeri ha scritto:
> Il 10/4/2013 6:32 AM, Mark Hadfield ha scritto:
>> There's a second issue. In the output of "/usr/bin/nf-config --all"
>> (below) a -no-undefined option is printed. This is not a valid option
>> for gfortran.
>>
>> With these two issues fixed I can compile and link Fortran 90 programs
>> that use the netCDF Fortran interface.
>>
>> ---------------------------------------------
>> $ /usr/bin/nf-config --all
>>
>> This netCDF-Fortran 4.2 has been built with the following features:
>>
>> --cc -> gcc
>> --cflags -> -I/usr/include
>> --libs -> -L/usr/lib -no-undefined -lnetcdf -lnetcdf
>>
>> --fc -> gfortran
>> --fflags -> -g -O2 -pipe -I/usr/include
>> --flibs -> -L/usr/lib -lnetcdff -no-undefined -lnetcdf -lnetcdf
>> --has-f90 -> yes
>>
>> --has-nc2 -> yes
>> --has-nc4 -> yes
>>
>> --prefix -> /usr
>> --includedir-> /usr/include
>> --version -> netCDF-Fortran 4.2
>>
>>
>>
>>
>> Dr Mark Hadfield
>
> Noted.
> I will rebuild the package reusing the configuration used on
> cygwin 64 bit package.
>
>
> $ /usr/bin/nf-config --all
>
> This netCDF-Fortran 4.2 has been built with the following features:
>
> --cc -> gcc
> --cflags -> -I/usr/include
> --libs -> -L/usr/lib -lnetcdf -lnetcdf
>
> --fc -> gfortran
> --fflags -> -ggdb -O2 -pipe
> -fdebug-prefix-map=/pub/devel/netcdf/netcdf-fortran-4.2-2/build=/usr/src/debug/netcdf-fortran-4.2-2
> -fdebug-prefix-map=/pub/devel/netcdf/netcdf-fortran-4.2-2/src/netcdf-fortran-4.2=/usr/src/debug/netcdf-fortran-4.2-2
> -I/usr/include
> --flibs -> -L/usr/lib -lnetcdff -lnetcdf -lnetcdf
> --has-f90 -> yes
>
> --has-nc2 -> yes
> --has-nc4 -> yes
>
> --prefix -> /usr
> --includedir-> /usr/include
> --version -> netCDF-Fortran 4.2
>
>
> Regards
> Marco
>
>
4.2-3 uploaded
--
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
next prev parent reply other threads:[~2013-10-04 9:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 4:11 Mark Hadfield
2013-10-04 4:32 ` Mark Hadfield
2013-10-04 8:57 ` marco atzeri
2013-10-04 9:57 ` marco atzeri [this message]
2013-10-06 21:50 ` Mark Hadfield
[not found] ` <A4BDD8E3859F92478F09D5AACD6D79C0956EF4DC@welwexmb01.niwa.local>
2013-10-07 1:46 ` marco atzeri
2015-01-20 23:50 Mark Hadfield
2015-01-21 4:40 Mark Hadfield
2015-01-21 9:02 ` Marco Atzeri
2016-02-29 22:40 Mark Hadfield
2016-03-01 5:35 ` 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=524E90E4.80207@gmail.com \
--to=marco.atzeri@gmail.com \
--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).