[Met_help] [rt.rap.ucar.edu #79100] History for question about compiling GRIB2 C-Library (UNCLASSIFIED)
Julie Prestopnik via RT
met_help at ucar.edu
Fri Jan 13 09:56:40 MST 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
CLASSIFICATION: UNCLASSIFIED
Unlike zlib, png and jasper which involved the running of ./configure before
running make, unpacking of g2clib failed to produce a configure script. The
README which was produced doesn't seem to provide much info about running
./configure. Is this a problem? The MET tutorial and User's Guide describe
some specific requirement for compiling with or without the option
-D__64BIT, but it is not clear how this option is specified. Could you
clarify on this issue? Also, what are the considerations which would help
the user choose between a configuration with the D__64BIT option vs a
configuration without it. I am progressing with installing MET V5.2 and
would like GRIB2 support.
Thanks.
R/
John
Mr John W. Raby, Meteorologist
U.S. Army Research Laboratory
White Sands Missile Range, NM 88002
(575) 678-2004 DSN 258-2004
FAX (575) 678-1230 DSN 258-1230
Email: john.w.raby2.civ at mail.mil
CLASSIFICATION: UNCLASSIFIED
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Julie Prestopnik
Time: Fri Jan 06 14:20:49 2017
Hi John.
Support for GRIB2 is disabled by default in MET. However, since you
would
like support for GRIB2 files you will need to compile the GRIB2C
Library
and enable GRIB2 support when configuring MET with" *--enable-grib2*".
I believe you would want to use the 64 bit flag if you were running on
a 64
bit machine. You would do that by setting *CFLAGS="-D__64BIT__"*,
either
with setenv or with export (for bash). You just need to make sure
that if
you configure the GRIB2C library in this way, you also configure MET
in
this way. Compiling MET and the GRIB2C library inconsistently may
result
in a segmentation fault when reading GRIB2 files.
To compile the GRIB2C library, please do the following:
# Get the GRIB2C library
wget http://www.nco.ncep.noaa.gov/pmb/codes/GRIB2/g2clib-1.6.0.tar
# Untar it
tar -xvf g2clib-1.6.0.tar
cd g2clib-1.6.0
# Open up and edit the "makefile"
# Set INC =-I/path/for/include/files
# Please make sure to include all idirectories where include files
# can be found (jasper/*.h and png.h pngconf.h zconf.h zlib.h)
# Compile it
make
I hope that helps!
Julie
On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
> Queue: met_help
> Subject: question about compiling GRIB2 C-Library
(UNCLASSIFIED)
> Owner: Nobody
> Requestors: john.w.raby2.civ at mail.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
>
> CLASSIFICATION: UNCLASSIFIED
>
> Unlike zlib, png and jasper which involved the running of
./configure
> before
> running make, unpacking of g2clib failed to produce a configure
script. The
> README which was produced doesn't seem to provide much info about
running
> ./configure. Is this a problem? The MET tutorial and User's Guide
describe
> some specific requirement for compiling with or without the option
> -D__64BIT, but it is not clear how this option is specified. Could
you
> clarify on this issue? Also, what are the considerations which would
help
> the user choose between a configuration with the D__64BIT option vs
a
> configuration without it. I am progressing with installing MET V5.2
and
> would like GRIB2 support.
>
> Thanks.
>
> R/
> John
>
> Mr John W. Raby, Meteorologist
> U.S. Army Research Laboratory
> White Sands Missile Range, NM 88002
> (575) 678-2004 DSN 258-2004
> FAX (575) 678-1230 DSN 258-1230
> Email: john.w.raby2.civ at mail.mil
>
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Fri Jan 06 15:39:50 2017
CLASSIFICATION: UNCLASSIFIED
Julie -
Thanks for your response.
Regarding support for GRIB2, I'll make a note of the MET configuration
option
you mentioned so I can use it when the time comes.
I checked the system and it uses 64-bit processors, so I'll use that
option
for compiling GRIB2C. The MET User's Guide provides the setting
(CFLAGS="-D__64BIT__") for MET. Is this setting made by opening and
editing
the makefile for MET?
I'm at the point in the GRIB2C compile steps you mention below where
I'm ready
to edit the makefile. I confirmed the version I used is the same as
the one
you mentioned. (g2clib-1.6.0.tar)
Thanks for the tip on the include files when editing the makefile.
Before running make, do I have to also edit the makefile to implement
the
option for 64-bit? ("-D__64BIT__" is the setting according the MET
User's
Guide).
R/
John
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Friday, January 06, 2017 2:21 PM
To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question about
compiling GRIB2 C-Library (UNCLASSIFIED)
All active links contained in this email were disabled. Please verify
the
identity of the sender, and confirm the authenticity of all links
contained
within the message prior to copying and pasting the address to a Web
browser.
----
Hi John.
Support for GRIB2 is disabled by default in MET. However, since you
would
like support for GRIB2 files you will need to compile the GRIB2C
Library and
enable GRIB2 support when configuring MET with" *--enable-grib2*".
I believe you would want to use the 64 bit flag if you were running on
a 64
bit machine. You would do that by setting *CFLAGS="-D__64BIT__"*,
either with
setenv or with export (for bash). You just need to make sure that if
you
configure the GRIB2C library in this way, you also configure MET in
this way.
Compiling MET and the GRIB2C library inconsistently may result in a
segmentation fault when reading GRIB2 files.
To compile the GRIB2C library, please do the following:
# Get the GRIB2C library
wget Caution-http://www.nco.ncep.noaa.gov/pmb/codes/GRIB2/g2clib-
1.6.0.tar
# Untar it
tar -xvf g2clib-1.6.0.tar
cd g2clib-1.6.0
# Open up and edit the "makefile"
# Set INC =-I/path/for/include/files
# Please make sure to include all idirectories where include files
# can be found (jasper/*.h and png.h pngconf.h zconf.h zlib.h)
# Compile it
make
I hope that helps!
Julie
On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
> Queue: met_help
> Subject: question about compiling GRIB2 C-Library
(UNCLASSIFIED)
> Owner: Nobody
> Requestors: john.w.raby2.civ at mail.mil
> Status: new
> Ticket <Caution-url:
> Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
>
> CLASSIFICATION: UNCLASSIFIED
>
> Unlike zlib, png and jasper which involved the running of
./configure
> before running make, unpacking of g2clib failed to produce a
configure
> script. The README which was produced doesn't seem to provide much
> info about running ./configure. Is this a problem? The MET tutorial
> and User's Guide describe some specific requirement for compiling
with
> or without the option -D__64BIT, but it is not clear how this option
> is specified. Could you clarify on this issue? Also, what are the
> considerations which would help the user choose between a
> configuration with the D__64BIT option vs a configuration without
it.
> I am progressing with installing MET V5.2 and would like GRIB2
> support.
>
> Thanks.
>
> R/
> John
>
> Mr John W. Raby, Meteorologist
> U.S. Army Research Laboratory
> White Sands Missile Range, NM 88002
> (575) 678-2004 DSN 258-2004
> FAX (575) 678-1230 DSN 258-1230
> Email: john.w.raby2.civ at mail.mil
>
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research Research Applications
Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
CLASSIFICATION: UNCLASSIFIED
------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Fri Jan 06 15:58:08 2017
CLASSIFICATION: UNCLASSIFIED
Julie -
I misread your email and later found the answer to one of my my
questions: "
The MET User's Guide provides the setting
(CFLAGS="-D__64BIT__") for MET. Is this setting made by opening and
editing
the makefile for MET? The answer is that the setting is done using
export as
you pointed out. Is the same export command used for GRIB2C?
(CFLAGS="-D__64BIT__")
Sorry for the confusion.
R/
John
-----Original Message-----
From: Raby, John W CIV USARMY RDECOM ARL (US)
Sent: Friday, January 06, 2017 3:40 PM
To: 'met_help at ucar.edu' <met_help at ucar.edu>
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about
compiling GRIB2 C-Library (UNCLASSIFIED)
CLASSIFICATION: UNCLASSIFIED
Julie -
Thanks for your response.
Regarding support for GRIB2, I'll make a note of the MET configuration
option
you mentioned so I can use it when the time comes.
I checked the system and it uses 64-bit processors, so I'll use that
option
for compiling GRIB2C. The MET User's Guide provides the setting
(CFLAGS="-D__64BIT__") for MET. Is this setting made by opening and
editing
the makefile for MET?
I'm at the point in the GRIB2C compile steps you mention below where
I'm ready
to edit the makefile. I confirmed the version I used is the same as
the one
you mentioned. (g2clib-1.6.0.tar)
Thanks for the tip on the include files when editing the makefile.
Before running make, do I have to also edit the makefile to implement
the
option for 64-bit? ("-D__64BIT__" is the setting according the MET
User's
Guide).
R/
John
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Friday, January 06, 2017 2:21 PM
To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question about
compiling GRIB2 C-Library (UNCLASSIFIED)
All active links contained in this email were disabled. Please verify
the
identity of the sender, and confirm the authenticity of all links
contained
within the message prior to copying and pasting the address to a Web
browser.
----
Hi John.
Support for GRIB2 is disabled by default in MET. However, since you
would
like support for GRIB2 files you will need to compile the GRIB2C
Library and
enable GRIB2 support when configuring MET with" *--enable-grib2*".
I believe you would want to use the 64 bit flag if you were running on
a 64
bit machine. You would do that by setting *CFLAGS="-D__64BIT__"*,
either with
setenv or with export (for bash). You just need to make sure that if
you
configure the GRIB2C library in this way, you also configure MET in
this way.
Compiling MET and the GRIB2C library inconsistently may result in a
segmentation fault when reading GRIB2 files.
To compile the GRIB2C library, please do the following:
# Get the GRIB2C library
wget Caution-http://www.nco.ncep.noaa.gov/pmb/codes/GRIB2/g2clib-
1.6.0.tar
# Untar it
tar -xvf g2clib-1.6.0.tar
cd g2clib-1.6.0
# Open up and edit the "makefile"
# Set INC =-I/path/for/include/files
# Please make sure to include all idirectories where include files
# can be found (jasper/*.h and png.h pngconf.h zconf.h zlib.h)
# Compile it
make
I hope that helps!
Julie
On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
> Queue: met_help
> Subject: question about compiling GRIB2 C-Library
(UNCLASSIFIED)
> Owner: Nobody
> Requestors: john.w.raby2.civ at mail.mil
> Status: new
> Ticket <Caution-url:
> Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
>
> CLASSIFICATION: UNCLASSIFIED
>
> Unlike zlib, png and jasper which involved the running of
./configure
> before running make, unpacking of g2clib failed to produce a
configure
> script. The README which was produced doesn't seem to provide much
> info about running ./configure. Is this a problem? The MET tutorial
> and User's Guide describe some specific requirement for compiling
with
> or without the option -D__64BIT, but it is not clear how this option
> is specified. Could you clarify on this issue? Also, what are the
> considerations which would help the user choose between a
> configuration with the D__64BIT option vs a configuration without
it.
> I am progressing with installing MET V5.2 and would like GRIB2
> support.
>
> Thanks.
>
> R/
> John
>
> Mr John W. Raby, Meteorologist
> U.S. Army Research Laboratory
> White Sands Missile Range, NM 88002
> (575) 678-2004 DSN 258-2004
> FAX (575) 678-1230 DSN 258-1230
> Email: john.w.raby2.civ at mail.mil
>
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research Research Applications
Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
CLASSIFICATION: UNCLASSIFIED
CLASSIFICATION: UNCLASSIFIED
------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Mon Jan 09 09:42:16 2017
CLASSIFICATION: UNCLASSIFIED
Julie -
I edited the makefile (attached as a wordpad file) as follows to
accomplish
the changes we discussed last week:
#INC=-I/nwprod/lib/include/-->in original makefile.
# The following INC settings were added by John Raby per the guidance
provided
by Julie Prestopnik from the MET Help Desk:
INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
#
# This "C" source code contains many uses of the C++
# comment style "//". Please make sure you include the
# appropriate compiler flag to allow the use of "//" comment
indicators.
#
# The following line sets the option for 64-bit.
CFLAGS= -O3 -g -m64 $(INC) $(DEFS) -D__64BIT__
CC=gcc
#LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in the
original makefile.
# The following line names the library to the same name as that
expected by
MET per the guidance from the MET User's Guide and the MET tutorial.
LIB=libgrib2c.a
**********************************************************************************************************************
Some comments about the edit changes:
I commented out the original INC statement and added 3 INC statements
to
account for jasper, zlib and PNG. I assume that multiple INC
statements to do
this will work, but I've never done this before. Not sure if you can
re-use
INC for different paths or whether you have to use INC1, INC2,
....INCX??
It looked like the option for 64-bit is specified in the makefile
rather than
using "export". Will this work?
I commented out the original statement " LIB=libg2c_v1.6.0.a" and
added a new
one to name the library as expected by MET.
Could you review my changes to see if they are correct?
Thanks.
R/
John
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Friday, January 06, 2017 2:21 PM
To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question about
compiling GRIB2 C-Library (UNCLASSIFIED)
All active links contained in this email were disabled. Please verify
the
identity of the sender, and confirm the authenticity of all links
contained
within the message prior to copying and pasting the address to a Web
browser.
----
Hi John.
Support for GRIB2 is disabled by default in MET. However, since you
would
like support for GRIB2 files you will need to compile the GRIB2C
Library and
enable GRIB2 support when configuring MET with" *--enable-grib2*".
I believe you would want to use the 64 bit flag if you were running on
a 64
bit machine. You would do that by setting *CFLAGS="-D__64BIT__"*,
either with
setenv or with export (for bash). You just need to make sure that if
you
configure the GRIB2C library in this way, you also configure MET in
this way.
Compiling MET and the GRIB2C library inconsistently may result in a
segmentation fault when reading GRIB2 files.
To compile the GRIB2C library, please do the following:
# Get the GRIB2C library
wget Caution-http://www.nco.ncep.noaa.gov/pmb/codes/GRIB2/g2clib-
1.6.0.tar
# Untar it
tar -xvf g2clib-1.6.0.tar
cd g2clib-1.6.0
# Open up and edit the "makefile"
# Set INC =-I/path/for/include/files
# Please make sure to include all idirectories where include files
# can be found (jasper/*.h and png.h pngconf.h zconf.h zlib.h)
# Compile it
make
I hope that helps!
Julie
On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
> Queue: met_help
> Subject: question about compiling GRIB2 C-Library
(UNCLASSIFIED)
> Owner: Nobody
> Requestors: john.w.raby2.civ at mail.mil
> Status: new
> Ticket <Caution-url:
> Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
>
> CLASSIFICATION: UNCLASSIFIED
>
> Unlike zlib, png and jasper which involved the running of
./configure
> before running make, unpacking of g2clib failed to produce a
configure
> script. The README which was produced doesn't seem to provide much
> info about running ./configure. Is this a problem? The MET tutorial
> and User's Guide describe some specific requirement for compiling
with
> or without the option -D__64BIT, but it is not clear how this option
> is specified. Could you clarify on this issue? Also, what are the
> considerations which would help the user choose between a
> configuration with the D__64BIT option vs a configuration without
it.
> I am progressing with installing MET V5.2 and would like GRIB2
> support.
>
> Thanks.
>
> R/
> John
>
> Mr John W. Raby, Meteorologist
> U.S. Army Research Laboratory
> White Sands Missile Range, NM 88002
> (575) 678-2004 DSN 258-2004
> FAX (575) 678-1230 DSN 258-1230
> Email: john.w.raby2.civ at mail.mil
>
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research Research Applications
Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
CLASSIFICATION: UNCLASSIFIED
------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Julie Prestopnik
Time: Mon Jan 09 10:49:14 2017
Hi John.
I see that you have some questions regarding compiling the GRIB2C
library.
Instead of the following:
INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
You'll want to have:
INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
-I/p/home/jraby/PNG/libpng-1.2.34/include/ -I/p/home/jraby/zlib/zlib-
1.2.8/include/
Please note that the -I and paths that follow are separated by spaces.
If
you keep what you have currently, I believe that it will only include
the
last one (zlib).
I see now that for the GRIB2C library, the setting of CFLAGS is done
inside
the makefile. That should work for compiling GRIB2C, however, for MET
you'll need to set the environment variable "CFLAGS" to include "
-D__64BIT__" using export.
Your change:
#LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in the
original makefile.
# The following line names the library to the same name as that
expected by
MET per the guidance from the MET User's Guide and the MET tutorial.
LIB=libgrib2c.a
looks correct to me.
Give that a try. Hopefully, everything will go smoothly. Please let
us
know if you encounter any other troubles.
Thanks!
Julie
On Mon, Jan 9, 2017 at 9:42 AM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
> CLASSIFICATION: UNCLASSIFIED
>
> Julie -
>
> I edited the makefile (attached as a wordpad file) as follows to
accomplish
> the changes we discussed last week:
>
> #INC=-I/nwprod/lib/include/-->in original makefile.
>
> # The following INC settings were added by John Raby per the
guidance
> provided
> by Julie Prestopnik from the MET Help Desk:
> INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> #
> # This "C" source code contains many uses of the C++
> # comment style "//". Please make sure you include the
> # appropriate compiler flag to allow the use of "//" comment
indicators.
> #
>
> # The following line sets the option for 64-bit.
> CFLAGS= -O3 -g -m64 $(INC) $(DEFS) -D__64BIT__
>
> CC=gcc
>
> #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in
the
> original makefile.
> # The following line names the library to the same name as that
expected by
> MET per the guidance from the MET User's Guide and the MET tutorial.
> LIB=libgrib2c.a
>
> ************************************************************
> **********************************************************
>
> Some comments about the edit changes:
>
> I commented out the original INC statement and added 3 INC
statements to
> account for jasper, zlib and PNG. I assume that multiple INC
statements to
> do
> this will work, but I've never done this before. Not sure if you can
re-use
> INC for different paths or whether you have to use INC1, INC2,
....INCX??
>
> It looked like the option for 64-bit is specified in the makefile
rather
> than
> using "export". Will this work?
>
> I commented out the original statement " LIB=libg2c_v1.6.0.a" and
added a
> new
> one to name the library as expected by MET.
>
> Could you review my changes to see if they are correct?
>
> Thanks.
>
> R/
> John
>
>
> -----Original Message-----
> From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> Sent: Friday, January 06, 2017 2:21 PM
> To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about
> compiling GRIB2 C-Library (UNCLASSIFIED)
>
> All active links contained in this email were disabled. Please
verify the
> identity of the sender, and confirm the authenticity of all links
contained
> within the message prior to copying and pasting the address to a Web
> browser.
>
>
>
>
> ----
>
> Hi John.
>
> Support for GRIB2 is disabled by default in MET. However, since you
would
> like support for GRIB2 files you will need to compile the GRIB2C
Library
> and
> enable GRIB2 support when configuring MET with" *--enable-grib2*".
>
> I believe you would want to use the 64 bit flag if you were running
on a 64
> bit machine. You would do that by setting *CFLAGS="-D__64BIT__"*,
either
> with
> setenv or with export (for bash). You just need to make sure that
if you
> configure the GRIB2C library in this way, you also configure MET in
this
> way.
> Compiling MET and the GRIB2C library inconsistently may result in a
> segmentation fault when reading GRIB2 files.
>
> To compile the GRIB2C library, please do the following:
>
> # Get the GRIB2C library
> wget Caution-http://www.nco.ncep.noaa.gov/pmb/codes/GRIB2/
> g2clib-1.6.0.tar
>
> # Untar it
> tar -xvf g2clib-1.6.0.tar
> cd g2clib-1.6.0
>
> # Open up and edit the "makefile"
> # Set INC =-I/path/for/include/files
> # Please make sure to include all idirectories where include
files
> # can be found (jasper/*.h and png.h pngconf.h zconf.h
zlib.h)
>
> # Compile it
> make
>
> I hope that helps!
>
> Julie
>
>
> On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> > Transaction: Ticket created by john.w.raby2.civ at mail.mil
> > Queue: met_help
> > Subject: question about compiling GRIB2 C-Library
(UNCLASSIFIED)
> > Owner: Nobody
> > Requestors: john.w.raby2.civ at mail.mil
> > Status: new
> > Ticket <Caution-url:
> > Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
> >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> > Unlike zlib, png and jasper which involved the running of
./configure
> > before running make, unpacking of g2clib failed to produce a
configure
> > script. The README which was produced doesn't seem to provide much
> > info about running ./configure. Is this a problem? The MET
tutorial
> > and User's Guide describe some specific requirement for compiling
with
> > or without the option -D__64BIT, but it is not clear how this
option
> > is specified. Could you clarify on this issue? Also, what are the
> > considerations which would help the user choose between a
> > configuration with the D__64BIT option vs a configuration without
it.
> > I am progressing with installing MET V5.2 and would like GRIB2
> > support.
> >
> > Thanks.
> >
> > R/
> > John
> >
> > Mr John W. Raby, Meteorologist
> > U.S. Army Research Laboratory
> > White Sands Missile Range, NM 88002
> > (575) 678-2004 DSN 258-2004
> > FAX (575) 678-1230 DSN 258-1230
> > Email: john.w.raby2.civ at mail.mil
> >
> >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> >
>
>
> --
> Julie Prestopnik
> National Center for Atmospheric Research Research Applications
Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Mon Jan 09 12:18:27 2017
CLASSIFICATION: UNCLASSIFIED
Julie -
Thanks for reviewing the makefile and providing feedback. I will let
you know
how it worked.
R/
John
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Monday, January 09, 2017 10:49 AM
To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about
compiling GRIB2 C-Library (UNCLASSIFIED)
All active links contained in this email were disabled. Please verify
the
identity of the sender, and confirm the authenticity of all links
contained
within the message prior to copying and pasting the address to a Web
browser.
----
Hi John.
I see that you have some questions regarding compiling the GRIB2C
library.
Instead of the following:
INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
You'll want to have:
INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
-I/p/home/jraby/PNG/libpng-1.2.34/include/ -I/p/home/jraby/zlib/zlib-
1.2.8/include/
Please note that the -I and paths that follow are separated by spaces.
If you
keep what you have currently, I believe that it will only include the
last one
(zlib).
I see now that for the GRIB2C library, the setting of CFLAGS is done
inside
the makefile. That should work for compiling GRIB2C, however, for MET
you'll
need to set the environment variable "CFLAGS" to include "
-D__64BIT__" using export.
Your change:
#LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in the
original makefile.
# The following line names the library to the same name as that
expected by
MET per the guidance from the MET User's Guide and the MET tutorial.
LIB=libgrib2c.a
looks correct to me.
Give that a try. Hopefully, everything will go smoothly. Please let
us know
if you encounter any other troubles.
Thanks!
Julie
On Mon, Jan 9, 2017 at 9:42 AM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> <Caution-url:
> Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
> CLASSIFICATION: UNCLASSIFIED
>
> Julie -
>
> I edited the makefile (attached as a wordpad file) as follows to
> accomplish the changes we discussed last week:
>
> #INC=-I/nwprod/lib/include/-->in original makefile.
>
> # The following INC settings were added by John Raby per the
guidance
> provided by Julie Prestopnik from the MET Help Desk:
> INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> #
> # This "C" source code contains many uses of the C++
> # comment style "//". Please make sure you include the
> # appropriate compiler flag to allow the use of "//" comment
indicators.
> #
>
> # The following line sets the option for 64-bit.
> CFLAGS= -O3 -g -m64 $(INC) $(DEFS) -D__64BIT__
>
> CC=gcc
>
> #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in
the
> original makefile.
> # The following line names the library to the same name as that
> expected by MET per the guidance from the MET User's Guide and the
MET
> tutorial.
> LIB=libgrib2c.a
>
> ************************************************************
> **********************************************************
>
> Some comments about the edit changes:
>
> I commented out the original INC statement and added 3 INC
statements
> to account for jasper, zlib and PNG. I assume that multiple INC
> statements to do this will work, but I've never done this before.
Not
> sure if you can re-use INC for different paths or whether you have
to
> use INC1, INC2, ....INCX??
>
> It looked like the option for 64-bit is specified in the makefile
> rather than using "export". Will this work?
>
> I commented out the original statement " LIB=libg2c_v1.6.0.a" and
> added a new one to name the library as expected by MET.
>
> Could you review my changes to see if they are correct?
>
> Thanks.
>
> R/
> John
>
>
> -----Original Message-----
> From: Julie Prestopnik via RT [Caution-mailto:met_help at ucar.edu]
> Sent: Friday, January 06, 2017 2:21 PM
> To: Raby, John W CIV USARMY RDECOM ARL (US)
> <john.w.raby2.civ at mail.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about
> compiling GRIB2 C-Library (UNCLASSIFIED)
>
> All active links contained in this email were disabled. Please
verify
> the identity of the sender, and confirm the authenticity of all
links
> contained within the message prior to copying and pasting the
address
> to a Web browser.
>
>
>
>
> ----
>
> Hi John.
>
> Support for GRIB2 is disabled by default in MET. However, since you
> would like support for GRIB2 files you will need to compile the
GRIB2C
> Library and enable GRIB2 support when configuring MET with"
> *--enable-grib2*".
>
> I believe you would want to use the 64 bit flag if you were running
on
> a 64 bit machine. You would do that by setting
> *CFLAGS="-D__64BIT__"*, either with setenv or with export (for
bash).
> You just need to make sure that if you configure the GRIB2C library
in
> this way, you also configure MET in this way.
> Compiling MET and the GRIB2C library inconsistently may result in a
> segmentation fault when reading GRIB2 files.
>
> To compile the GRIB2C library, please do the following:
>
> # Get the GRIB2C library
> wget Caution-Caution-
http://www.nco.ncep.noaa.gov/pmb/codes/GRIB2/
> g2clib-1.6.0.tar
>
> # Untar it
> tar -xvf g2clib-1.6.0.tar
> cd g2clib-1.6.0
>
> # Open up and edit the "makefile"
> # Set INC =-I/path/for/include/files
> # Please make sure to include all idirectories where include
files
> # can be found (jasper/*.h and png.h pngconf.h zconf.h
zlib.h)
>
> # Compile it
> make
>
> I hope that helps!
>
> Julie
>
>
> On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> > Transaction: Ticket created by john.w.raby2.civ at mail.mil
> > Queue: met_help
> > Subject: question about compiling GRIB2 C-Library
(UNCLASSIFIED)
> > Owner: Nobody
> > Requestors: john.w.raby2.civ at mail.mil
> > Status: new
> > Ticket <Caution-Caution-url:
> > Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79
> > 100 >
> >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> > Unlike zlib, png and jasper which involved the running of
> > ./configure before running make, unpacking of g2clib failed to
> > produce a configure script. The README which was produced doesn't
> > seem to provide much info about running ./configure. Is this a
> > problem? The MET tutorial and User's Guide describe some specific
> > requirement for compiling with or without the option -D__64BIT,
but
> > it is not clear how this option is specified. Could you clarify on
> > this issue? Also, what are the considerations which would help the
> > user choose between a configuration with the D__64BIT option vs a
> > configuration without it.
> > I am progressing with installing MET V5.2 and would like GRIB2
> > support.
> >
> > Thanks.
> >
> > R/
> > John
> >
> > Mr John W. Raby, Meteorologist
> > U.S. Army Research Laboratory
> > White Sands Missile Range, NM 88002
> > (575) 678-2004 DSN 258-2004
> > FAX (575) 678-1230 DSN 258-1230
> > Email: john.w.raby2.civ at mail.mil
> >
> >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> >
>
>
> --
> Julie Prestopnik
> National Center for Atmospheric Research Research Applications
> Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research Research Applications
Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
CLASSIFICATION: UNCLASSIFIED
------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Mon Jan 09 14:49:52 2017
CLASSIFICATION: UNCLASSIFIED
Julie -
I edited the makefile to incorporate the changes. Then on running make
I
noticed a potential issue which appeared in the screen dialog. The
following
statement appeared numerous times:
gcc: /p/home/jraby/PNG/libpng-1.2.34/include: linker input file unused
because
linking not done
gcc: /p/home/jraby/zlib/zlib-1.2.8/include: linker input file unused
because
linking not done
ar -ruv libgrib2c.a seekgb.o
a - seekgb.o
rm -f seekgb.o
excalibur:~jraby/grib2c/g2clib-1.6.0
Does this indicate a problem which needs to be fixed before the
install?
I have one question which occurred to me as I was editing the
makefile. I
noticed that there is s statement "CC=gcc". Does this refer to the
value of
the common environment variable $CC which for my system (Excalibur) is
"icc"
not "gcc". Maybe this is no issue at all, but I wanted to ask you
about it in
case it is.
I also have a question about compiling the HDF-EOS library. Following
the MET
tutorial, I performed all the steps except the last one (cp
include/*.h
../../include/.). At the point where I am supposed to execute this
statement,
I am sitting in the following directory:
/p/home/jraby/hdfeos/hdfeos
If I execute the cp statement as is, it looks for the target dir up in
my home
(jraby) and there is no "include" dir in jraby. I need more info as to
what
the intended destination is or where the target dir is supposed to be
located
so I can modify the path I use accordingly.
Thanks.
R/
John
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Monday, January 09, 2017 10:49 AM
To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about
compiling GRIB2 C-Library (UNCLASSIFIED)
All active links contained in this email were disabled. Please verify
the
identity of the sender, and confirm the authenticity of all links
contained
within the message prior to copying and pasting the address to a Web
browser.
----
Hi John.
I see that you have some questions regarding compiling the GRIB2C
library.
Instead of the following:
INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
You'll want to have:
INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
-I/p/home/jraby/PNG/libpng-1.2.34/include/ -I/p/home/jraby/zlib/zlib-
1.2.8/include/
Please note that the -I and paths that follow are separated by spaces.
If you
keep what you have currently, I believe that it will only include the
last one
(zlib).
I see now that for the GRIB2C library, the setting of CFLAGS is done
inside
the makefile. That should work for compiling GRIB2C, however, for MET
you'll
need to set the environment variable "CFLAGS" to include "
-D__64BIT__" using export.
Your change:
#LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in the
original makefile.
# The following line names the library to the same name as that
expected by
MET per the guidance from the MET User's Guide and the MET tutorial.
LIB=libgrib2c.a
looks correct to me.
Give that a try. Hopefully, everything will go smoothly. Please let
us know
if you encounter any other troubles.
Thanks!
Julie
On Mon, Jan 9, 2017 at 9:42 AM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> <Caution-url:
> Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
> CLASSIFICATION: UNCLASSIFIED
>
> Julie -
>
> I edited the makefile (attached as a wordpad file) as follows to
> accomplish the changes we discussed last week:
>
> #INC=-I/nwprod/lib/include/-->in original makefile.
>
> # The following INC settings were added by John Raby per the
guidance
> provided by Julie Prestopnik from the MET Help Desk:
> INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> #
> # This "C" source code contains many uses of the C++
> # comment style "//". Please make sure you include the
> # appropriate compiler flag to allow the use of "//" comment
indicators.
> #
>
> # The following line sets the option for 64-bit.
> CFLAGS= -O3 -g -m64 $(INC) $(DEFS) -D__64BIT__
>
> CC=gcc
>
> #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in
the
> original makefile.
> # The following line names the library to the same name as that
> expected by MET per the guidance from the MET User's Guide and the
MET
> tutorial.
> LIB=libgrib2c.a
>
> ************************************************************
> **********************************************************
>
> Some comments about the edit changes:
>
> I commented out the original INC statement and added 3 INC
statements
> to account for jasper, zlib and PNG. I assume that multiple INC
> statements to do this will work, but I've never done this before.
Not
> sure if you can re-use INC for different paths or whether you have
to
> use INC1, INC2, ....INCX??
>
> It looked like the option for 64-bit is specified in the makefile
> rather than using "export". Will this work?
>
> I commented out the original statement " LIB=libg2c_v1.6.0.a" and
> added a new one to name the library as expected by MET.
>
> Could you review my changes to see if they are correct?
>
> Thanks.
>
> R/
> John
>
>
> -----Original Message-----
> From: Julie Prestopnik via RT [Caution-mailto:met_help at ucar.edu]
> Sent: Friday, January 06, 2017 2:21 PM
> To: Raby, John W CIV USARMY RDECOM ARL (US)
> <john.w.raby2.civ at mail.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about
> compiling GRIB2 C-Library (UNCLASSIFIED)
>
> All active links contained in this email were disabled. Please
verify
> the identity of the sender, and confirm the authenticity of all
links
> contained within the message prior to copying and pasting the
address
> to a Web browser.
>
>
>
>
> ----
>
> Hi John.
>
> Support for GRIB2 is disabled by default in MET. However, since you
> would like support for GRIB2 files you will need to compile the
GRIB2C
> Library and enable GRIB2 support when configuring MET with"
> *--enable-grib2*".
>
> I believe you would want to use the 64 bit flag if you were running
on
> a 64 bit machine. You would do that by setting
> *CFLAGS="-D__64BIT__"*, either with setenv or with export (for
bash).
> You just need to make sure that if you configure the GRIB2C library
in
> this way, you also configure MET in this way.
> Compiling MET and the GRIB2C library inconsistently may result in a
> segmentation fault when reading GRIB2 files.
>
> To compile the GRIB2C library, please do the following:
>
> # Get the GRIB2C library
> wget Caution-Caution-
http://www.nco.ncep.noaa.gov/pmb/codes/GRIB2/
> g2clib-1.6.0.tar
>
> # Untar it
> tar -xvf g2clib-1.6.0.tar
> cd g2clib-1.6.0
>
> # Open up and edit the "makefile"
> # Set INC =-I/path/for/include/files
> # Please make sure to include all idirectories where include
files
> # can be found (jasper/*.h and png.h pngconf.h zconf.h
zlib.h)
>
> # Compile it
> make
>
> I hope that helps!
>
> Julie
>
>
> On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> > Transaction: Ticket created by john.w.raby2.civ at mail.mil
> > Queue: met_help
> > Subject: question about compiling GRIB2 C-Library
(UNCLASSIFIED)
> > Owner: Nobody
> > Requestors: john.w.raby2.civ at mail.mil
> > Status: new
> > Ticket <Caution-Caution-url:
> > Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79
> > 100 >
> >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> > Unlike zlib, png and jasper which involved the running of
> > ./configure before running make, unpacking of g2clib failed to
> > produce a configure script. The README which was produced doesn't
> > seem to provide much info about running ./configure. Is this a
> > problem? The MET tutorial and User's Guide describe some specific
> > requirement for compiling with or without the option -D__64BIT,
but
> > it is not clear how this option is specified. Could you clarify on
> > this issue? Also, what are the considerations which would help the
> > user choose between a configuration with the D__64BIT option vs a
> > configuration without it.
> > I am progressing with installing MET V5.2 and would like GRIB2
> > support.
> >
> > Thanks.
> >
> > R/
> > John
> >
> > Mr John W. Raby, Meteorologist
> > U.S. Army Research Laboratory
> > White Sands Missile Range, NM 88002
> > (575) 678-2004 DSN 258-2004
> > FAX (575) 678-1230 DSN 258-1230
> > Email: john.w.raby2.civ at mail.mil
> >
> >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> >
>
>
> --
> Julie Prestopnik
> National Center for Atmospheric Research Research Applications
> Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research Research Applications
Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
CLASSIFICATION: UNCLASSIFIED
------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Julie Prestopnik
Time: Tue Jan 10 09:23:00 2017
Hi John.
I see you have a question about the message " linker input file unused
because linking not done". I think that may indicate a problem which
would
need to be fixed before the install.
The statement "CC=gcc" does this refer to the value of the common
environment variable $CC which you said for your system is "icc".
Please
change that value in the makefile for the GRIB2C library. The same
family
of compilers should be used to build all of the external libraries and
MET. Mixing GNU compilers with Intel compilers is not a good idea.
Please change that "gcc" value to "icc" in the makefile and try it
again.
Please let me know if that makes those messages go away.
Regarding your question about copying over the header files for the
HDF-EOS
libraries, I believe you want to copy them over the include directory
in
your *${INSTALL_DIR}*. Please give that a try and let us know if you
experience any problems. In the meantime, I'll work on clarifying why
it
currently says "cp include/*.h ../../include/".
Thanks,
Julie
On Mon, Jan 9, 2017 at 2:49 PM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
> CLASSIFICATION: UNCLASSIFIED
>
> Julie -
>
> I edited the makefile to incorporate the changes. Then on running
make I
> noticed a potential issue which appeared in the screen dialog. The
> following
> statement appeared numerous times:
>
> gcc: /p/home/jraby/PNG/libpng-1.2.34/include: linker input file
unused
> because
> linking not done
> gcc: /p/home/jraby/zlib/zlib-1.2.8/include: linker input file unused
> because
> linking not done
> ar -ruv libgrib2c.a seekgb.o
> a - seekgb.o
> rm -f seekgb.o
> excalibur:~jraby/grib2c/g2clib-1.6.0
>
> Does this indicate a problem which needs to be fixed before the
install?
>
> I have one question which occurred to me as I was editing the
makefile. I
> noticed that there is s statement "CC=gcc". Does this refer to the
value of
> the common environment variable $CC which for my system (Excalibur)
is
> "icc"
> not "gcc". Maybe this is no issue at all, but I wanted to ask you
about it
> in
> case it is.
>
> I also have a question about compiling the HDF-EOS library.
Following the
> MET
> tutorial, I performed all the steps except the last one (cp
include/*.h
> ../../include/.). At the point where I am supposed to execute this
> statement,
> I am sitting in the following directory:
>
> /p/home/jraby/hdfeos/hdfeos
>
> If I execute the cp statement as is, it looks for the target dir up
in my
> home
> (jraby) and there is no "include" dir in jraby. I need more info as
to what
> the intended destination is or where the target dir is supposed to
be
> located
> so I can modify the path I use accordingly.
>
> Thanks.
>
> R/
> John
>
> -----Original Message-----
> From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> Sent: Monday, January 09, 2017 10:49 AM
> To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about
> compiling GRIB2 C-Library (UNCLASSIFIED)
>
> All active links contained in this email were disabled. Please
verify the
> identity of the sender, and confirm the authenticity of all links
contained
> within the message prior to copying and pasting the address to a Web
> browser.
>
>
>
>
> ----
>
> Hi John.
>
> I see that you have some questions regarding compiling the GRIB2C
library.
> Instead of the following:
>
> INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
>
> You'll want to have:
>
> INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> -I/p/home/jraby/PNG/libpng-1.2.34/include/
-I/p/home/jraby/zlib/zlib-
> 1.2.8/include/
>
> Please note that the -I and paths that follow are separated by
spaces. If
> you
> keep what you have currently, I believe that it will only include
the last
> one
> (zlib).
>
> I see now that for the GRIB2C library, the setting of CFLAGS is done
inside
> the makefile. That should work for compiling GRIB2C, however, for
MET
> you'll
> need to set the environment variable "CFLAGS" to include "
> -D__64BIT__" using export.
>
> Your change:
>
> #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in
the
> original makefile.
> # The following line names the library to the same name as that
expected by
> MET per the guidance from the MET User's Guide and the MET tutorial.
> LIB=libgrib2c.a
>
> looks correct to me.
>
> Give that a try. Hopefully, everything will go smoothly. Please
let us
> know
> if you encounter any other troubles.
>
> Thanks!
>
> Julie
>
> On Mon, Jan 9, 2017 at 9:42 AM, Raby, John W USA CIV via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <Caution-url:
> > Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> > Julie -
> >
> > I edited the makefile (attached as a wordpad file) as follows to
> > accomplish the changes we discussed last week:
> >
> > #INC=-I/nwprod/lib/include/-->in original makefile.
> >
> > # The following INC settings were added by John Raby per the
guidance
> > provided by Julie Prestopnik from the MET Help Desk:
> > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> > INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> > #
> > # This "C" source code contains many uses of the C++
> > # comment style "//". Please make sure you include the
> > # appropriate compiler flag to allow the use of "//" comment
> indicators.
> > #
> >
> > # The following line sets the option for 64-bit.
> > CFLAGS= -O3 -g -m64 $(INC) $(DEFS) -D__64BIT__
> >
> > CC=gcc
> >
> > #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in
the
> > original makefile.
> > # The following line names the library to the same name as that
> > expected by MET per the guidance from the MET User's Guide and the
MET
> > tutorial.
> > LIB=libgrib2c.a
> >
> > ************************************************************
> > **********************************************************
> >
> > Some comments about the edit changes:
> >
> > I commented out the original INC statement and added 3 INC
statements
> > to account for jasper, zlib and PNG. I assume that multiple INC
> > statements to do this will work, but I've never done this before.
Not
> > sure if you can re-use INC for different paths or whether you have
to
> > use INC1, INC2, ....INCX??
> >
> > It looked like the option for 64-bit is specified in the makefile
> > rather than using "export". Will this work?
> >
> > I commented out the original statement " LIB=libg2c_v1.6.0.a" and
> > added a new one to name the library as expected by MET.
> >
> > Could you review my changes to see if they are correct?
> >
> > Thanks.
> >
> > R/
> > John
> >
> >
> > -----Original Message-----
> > From: Julie Prestopnik via RT [Caution-mailto:met_help at ucar.edu]
> > Sent: Friday, January 06, 2017 2:21 PM
> > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > <john.w.raby2.civ at mail.mil>
> > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about
> > compiling GRIB2 C-Library (UNCLASSIFIED)
> >
> > All active links contained in this email were disabled. Please
verify
> > the identity of the sender, and confirm the authenticity of all
links
> > contained within the message prior to copying and pasting the
address
> > to a Web browser.
> >
> >
> >
> >
> > ----
> >
> > Hi John.
> >
> > Support for GRIB2 is disabled by default in MET. However, since
you
> > would like support for GRIB2 files you will need to compile the
GRIB2C
> > Library and enable GRIB2 support when configuring MET with"
> > *--enable-grib2*".
> >
> > I believe you would want to use the 64 bit flag if you were
running on
> > a 64 bit machine. You would do that by setting
> > *CFLAGS="-D__64BIT__"*, either with setenv or with export (for
bash).
> > You just need to make sure that if you configure the GRIB2C
library in
> > this way, you also configure MET in this way.
> > Compiling MET and the GRIB2C library inconsistently may result in
a
> > segmentation fault when reading GRIB2 files.
> >
> > To compile the GRIB2C library, please do the following:
> >
> > # Get the GRIB2C library
> > wget Caution-Caution-
http://www.nco.ncep.noaa.gov/pmb/codes/GRIB2/
> > g2clib-1.6.0.tar
> >
> > # Untar it
> > tar -xvf g2clib-1.6.0.tar
> > cd g2clib-1.6.0
> >
> > # Open up and edit the "makefile"
> > # Set INC =-I/path/for/include/files
> > # Please make sure to include all idirectories where include
files
> > # can be found (jasper/*.h and png.h pngconf.h zconf.h
zlib.h)
> >
> > # Compile it
> > make
> >
> > I hope that helps!
> >
> > Julie
> >
> >
> > On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> > > Transaction: Ticket created by john.w.raby2.civ at mail.mil
> > > Queue: met_help
> > > Subject: question about compiling GRIB2 C-Library
(UNCLASSIFIED)
> > > Owner: Nobody
> > > Requestors: john.w.raby2.civ at mail.mil
> > > Status: new
> > > Ticket <Caution-Caution-url:
> > > Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79
> > > 100 >
> > >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > > Unlike zlib, png and jasper which involved the running of
> > > ./configure before running make, unpacking of g2clib failed to
> > > produce a configure script. The README which was produced
doesn't
> > > seem to provide much info about running ./configure. Is this a
> > > problem? The MET tutorial and User's Guide describe some
specific
> > > requirement for compiling with or without the option -D__64BIT,
but
> > > it is not clear how this option is specified. Could you clarify
on
> > > this issue? Also, what are the considerations which would help
the
> > > user choose between a configuration with the D__64BIT option vs
a
> > > configuration without it.
> > > I am progressing with installing MET V5.2 and would like GRIB2
> > > support.
> > >
> > > Thanks.
> > >
> > > R/
> > > John
> > >
> > > Mr John W. Raby, Meteorologist
> > > U.S. Army Research Laboratory
> > > White Sands Missile Range, NM 88002
> > > (575) 678-2004 DSN 258-2004
> > > FAX (575) 678-1230 DSN 258-1230
> > > Email: john.w.raby2.civ at mail.mil
> > >
> > >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > >
> >
> >
> > --
> > Julie Prestopnik
> > National Center for Atmospheric Research Research Applications
> > Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> >
>
>
> --
> Julie Prestopnik
> National Center for Atmospheric Research Research Applications
Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Tue Jan 10 11:03:38 2017
CLASSIFICATION: UNCLASSIFIED
Julie -
Thanks for diagnosing the issues I was having.
Regards running the g2clib makefile, after I edited the line CC=gcc
replacing gcc with icc, this time the make command ran and completed
immediately with no screen dialog except “Nothing to be done for
`all". No messages appeared.
Regards the copying of the HDF-EOS library header files from
/p/home/jraby/hdfeos/hdfeos to the ${INSTALL_DIR}
(/p/home/jraby/hdfeos/include) per your suggestion, I was able to do
this after creating the "include" dir in /p/home/jraby/hdfeos/. I used
the same cp command modified as follows:
cp include/*.h ../include/.
This populated the include dir with four .h files and completed the
last step required for compiling HDF-EOS per the tutorial.
I haven't started work on the MODE graphics libraries yet, but I did
see your response which will help me as I work through that.
R/
John
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, January 10, 2017 9:23 AM
To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about compiling GRIB2 C-Library (UNCLASSIFIED)
All active links contained in this email were disabled. Please verify
the identity of the sender, and confirm the authenticity of all links
contained within the message prior to copying and pasting the address
to a Web browser.
----
Hi John.
I see you have a question about the message " linker input file unused
because linking not done". I think that may indicate a problem which
would need to be fixed before the install.
The statement "CC=gcc" does this refer to the value of the common
environment variable $CC which you said for your system is "icc".
Please change that value in the makefile for the GRIB2C library. The
same family of compilers should be used to build all of the external
libraries and MET. Mixing GNU compilers with Intel compilers is not a
good idea.
Please change that "gcc" value to "icc" in the makefile and try it
again.
Please let me know if that makes those messages go away.
Regarding your question about copying over the header files for the
HDF-EOS libraries, I believe you want to copy them over the include
directory in your *${INSTALL_DIR}*. Please give that a try and let us
know if you experience any problems. In the meantime, I'll work on
clarifying why it currently says "cp include/*.h ../../include/".
Thanks,
Julie
On Mon, Jan 9, 2017 at 2:49 PM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> <Caution-url:
> Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
> CLASSIFICATION: UNCLASSIFIED
>
> Julie -
>
> I edited the makefile to incorporate the changes. Then on running
make
> I noticed a potential issue which appeared in the screen dialog. The
> following statement appeared numerous times:
>
> gcc: /p/home/jraby/PNG/libpng-1.2.34/include: linker input file
unused
> because linking not done
> gcc: /p/home/jraby/zlib/zlib-1.2.8/include: linker input file unused
> because linking not done ar -ruv libgrib2c.a seekgb.o a - seekgb.o
rm
> -f seekgb.o
> excalibur:~jraby/grib2c/g2clib-1.6.0
>
> Does this indicate a problem which needs to be fixed before the
install?
>
> I have one question which occurred to me as I was editing the
> makefile. I noticed that there is s statement "CC=gcc". Does this
> refer to the value of the common environment variable $CC which for
my
> system (Excalibur) is "icc"
> not "gcc". Maybe this is no issue at all, but I wanted to ask you
> about it in case it is.
>
> I also have a question about compiling the HDF-EOS library.
Following
> the MET tutorial, I performed all the steps except the last one (cp
> include/*.h ../../include/.). At the point where I am supposed to
> execute this statement, I am sitting in the following directory:
>
> /p/home/jraby/hdfeos/hdfeos
>
> If I execute the cp statement as is, it looks for the target dir up
in
> my home
> (jraby) and there is no "include" dir in jraby. I need more info as
to
> what the intended destination is or where the target dir is supposed
> to be located so I can modify the path I use accordingly.
>
> Thanks.
>
> R/
> John
>
> -----Original Message-----
> From: Julie Prestopnik via RT [Caution-mailto:met_help at ucar.edu]
> Sent: Monday, January 09, 2017 10:49 AM
> To: Raby, John W CIV USARMY RDECOM ARL (US)
> <john.w.raby2.civ at mail.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
> about compiling GRIB2 C-Library (UNCLASSIFIED)
>
> All active links contained in this email were disabled. Please
verify
> the identity of the sender, and confirm the authenticity of all
links
> contained within the message prior to copying and pasting the
address
> to a Web browser.
>
>
>
>
> ----
>
> Hi John.
>
> I see that you have some questions regarding compiling the GRIB2C
library.
> Instead of the following:
>
> INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
>
> You'll want to have:
>
> INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> -I/p/home/jraby/PNG/libpng-1.2.34/include/
-I/p/home/jraby/zlib/zlib-
> 1.2.8/include/
>
> Please note that the -I and paths that follow are separated by
spaces.
> If you keep what you have currently, I believe that it will only
> include the last one (zlib).
>
> I see now that for the GRIB2C library, the setting of CFLAGS is done
> inside the makefile. That should work for compiling GRIB2C,
however,
> for MET you'll need to set the environment variable "CFLAGS" to
> include "
> -D__64BIT__" using export.
>
> Your change:
>
> #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in
the
> original makefile.
> # The following line names the library to the same name as that
> expected by MET per the guidance from the MET User's Guide and the
MET tutorial.
> LIB=libgrib2c.a
>
> looks correct to me.
>
> Give that a try. Hopefully, everything will go smoothly. Please
let
> us know if you encounter any other troubles.
>
> Thanks!
>
> Julie
>
> On Mon, Jan 9, 2017 at 9:42 AM, Raby, John W USA CIV via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <Caution-Caution-url:
> > Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79
> > 100 >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> > Julie -
> >
> > I edited the makefile (attached as a wordpad file) as follows to
> > accomplish the changes we discussed last week:
> >
> > #INC=-I/nwprod/lib/include/-->in original makefile.
> >
> > # The following INC settings were added by John Raby per the
> > guidance provided by Julie Prestopnik from the MET Help Desk:
> > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> > INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> > #
> > # This "C" source code contains many uses of the C++
> > # comment style "//". Please make sure you include the
> > # appropriate compiler flag to allow the use of "//" comment
> indicators.
> > #
> >
> > # The following line sets the option for 64-bit.
> > CFLAGS= -O3 -g -m64 $(INC) $(DEFS) -D__64BIT__
> >
> > CC=gcc
> >
> > #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in
> > the original makefile.
> > # The following line names the library to the same name as that
> > expected by MET per the guidance from the MET User's Guide and the
> > MET tutorial.
> > LIB=libgrib2c.a
> >
> > ************************************************************
> > **********************************************************
> >
> > Some comments about the edit changes:
> >
> > I commented out the original INC statement and added 3 INC
> > statements to account for jasper, zlib and PNG. I assume that
> > multiple INC statements to do this will work, but I've never done
> > this before. Not sure if you can re-use INC for different paths or
> > whether you have to use INC1, INC2, ....INCX??
> >
> > It looked like the option for 64-bit is specified in the makefile
> > rather than using "export". Will this work?
> >
> > I commented out the original statement " LIB=libg2c_v1.6.0.a" and
> > added a new one to name the library as expected by MET.
> >
> > Could you review my changes to see if they are correct?
> >
> > Thanks.
> >
> > R/
> > John
> >
> >
> > -----Original Message-----
> > From: Julie Prestopnik via RT
> > [Caution-Caution-mailto:met_help at ucar.edu]
> > Sent: Friday, January 06, 2017 2:21 PM
> > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > <john.w.raby2.civ at mail.mil>
> > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
> > about compiling GRIB2 C-Library (UNCLASSIFIED)
> >
> > All active links contained in this email were disabled. Please
> > verify the identity of the sender, and confirm the authenticity of
> > all links contained within the message prior to copying and
pasting
> > the address to a Web browser.
> >
> >
> >
> >
> > ----
> >
> > Hi John.
> >
> > Support for GRIB2 is disabled by default in MET. However, since
you
> > would like support for GRIB2 files you will need to compile the
> > GRIB2C Library and enable GRIB2 support when configuring MET with"
> > *--enable-grib2*".
> >
> > I believe you would want to use the 64 bit flag if you were
running
> > on a 64 bit machine. You would do that by setting
> > *CFLAGS="-D__64BIT__"*, either with setenv or with export (for
bash).
> > You just need to make sure that if you configure the GRIB2C
library
> > in this way, you also configure MET in this way.
> > Compiling MET and the GRIB2C library inconsistently may result in
a
> > segmentation fault when reading GRIB2 files.
> >
> > To compile the GRIB2C library, please do the following:
> >
> > # Get the GRIB2C library
> > wget
> > Caution-Caution-Caution-
http://www.nco.ncep.noaa.gov/pmb/codes/GRIB2
> > /
> > g2clib-1.6.0.tar
> >
> > # Untar it
> > tar -xvf g2clib-1.6.0.tar
> > cd g2clib-1.6.0
> >
> > # Open up and edit the "makefile"
> > # Set INC =-I/path/for/include/files
> > # Please make sure to include all idirectories where include
files
> > # can be found (jasper/*.h and png.h pngconf.h zconf.h
zlib.h)
> >
> > # Compile it
> > make
> >
> > I hope that helps!
> >
> > Julie
> >
> >
> > On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> > > Transaction: Ticket created by john.w.raby2.civ at mail.mil
> > > Queue: met_help
> > > Subject: question about compiling GRIB2 C-Library
(UNCLASSIFIED)
> > > Owner: Nobody
> > > Requestors: john.w.raby2.civ at mail.mil
> > > Status: new
> > > Ticket <Caution-Caution-Caution-url:
> > > Caution-Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.
> > > html?id=79
> > > 100 >
> > >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > > Unlike zlib, png and jasper which involved the running of
> > > ./configure before running make, unpacking of g2clib failed to
> > > produce a configure script. The README which was produced
doesn't
> > > seem to provide much info about running ./configure. Is this a
> > > problem? The MET tutorial and User's Guide describe some
specific
> > > requirement for compiling with or without the option -D__64BIT,
> > > but it is not clear how this option is specified. Could you
> > > clarify on this issue? Also, what are the considerations which
> > > would help the user choose between a configuration with the
> > > D__64BIT option vs a configuration without it.
> > > I am progressing with installing MET V5.2 and would like GRIB2
> > > support.
> > >
> > > Thanks.
> > >
> > > R/
> > > John
> > >
> > > Mr John W. Raby, Meteorologist
> > > U.S. Army Research Laboratory
> > > White Sands Missile Range, NM 88002
> > > (575) 678-2004 DSN 258-2004
> > > FAX (575) 678-1230 DSN 258-1230
> > > Email: john.w.raby2.civ at mail.mil
> > >
> > >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > >
> >
> >
> > --
> > Julie Prestopnik
> > National Center for Atmospheric Research Research Applications
> > Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> >
>
>
> --
> Julie Prestopnik
> National Center for Atmospheric Research Research Applications
> Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research Research Applications
Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
CLASSIFICATION: UNCLASSIFIED
------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Tue Jan 10 15:52:05 2017
CLASSIFICATION: UNCLASSIFIED
Julie -
Regards the compiling of the GRIB2C library, I sent an email earlier
today
which mentioned that after I edited the makefile to change "gcc" to
"icc" per
your suggestion, I was able to run "make" and no messages about
"linking not
done" appeared.
I went ahead and ran "make install" in the following location
(${INSTALL_DIR))
or /p/home/jraby/grib2c/g2clib-1.6.0, but it was stopped with the
following
error:
> make install
make: *** No rule to make target `install'. Stop.
excalibur:~jraby/grib2c/g2clib-1.6.0
I'm not sure what the problem is.
R/
John
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, January 10, 2017 9:23 AM
To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about
compiling GRIB2 C-Library (UNCLASSIFIED)
All active links contained in this email were disabled. Please verify
the
identity of the sender, and confirm the authenticity of all links
contained
within the message prior to copying and pasting the address to a Web
browser.
----
Hi John.
I see you have a question about the message " linker input file unused
because
linking not done". I think that may indicate a problem which would
need to be
fixed before the install.
The statement "CC=gcc" does this refer to the value of the common
environment
variable $CC which you said for your system is "icc". Please change
that
value in the makefile for the GRIB2C library. The same family of
compilers
should be used to build all of the external libraries and MET. Mixing
GNU
compilers with Intel compilers is not a good idea.
Please change that "gcc" value to "icc" in the makefile and try it
again.
Please let me know if that makes those messages go away.
Regarding your question about copying over the header files for the
HDF-EOS
libraries, I believe you want to copy them over the include directory
in your
*${INSTALL_DIR}*. Please give that a try and let us know if you
experience
any problems. In the meantime, I'll work on clarifying why it
currently says
"cp include/*.h ../../include/".
Thanks,
Julie
On Mon, Jan 9, 2017 at 2:49 PM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> <Caution-url:
> Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
> CLASSIFICATION: UNCLASSIFIED
>
> Julie -
>
> I edited the makefile to incorporate the changes. Then on running
make
> I noticed a potential issue which appeared in the screen dialog. The
> following statement appeared numerous times:
>
> gcc: /p/home/jraby/PNG/libpng-1.2.34/include: linker input file
unused
> because linking not done
> gcc: /p/home/jraby/zlib/zlib-1.2.8/include: linker input file unused
> because linking not done ar -ruv libgrib2c.a seekgb.o a - seekgb.o
rm
> -f seekgb.o
> excalibur:~jraby/grib2c/g2clib-1.6.0
>
> Does this indicate a problem which needs to be fixed before the
install?
>
> I have one question which occurred to me as I was editing the
> makefile. I noticed that there is s statement "CC=gcc". Does this
> refer to the value of the common environment variable $CC which for
my
> system (Excalibur) is "icc"
> not "gcc". Maybe this is no issue at all, but I wanted to ask you
> about it in case it is.
>
> I also have a question about compiling the HDF-EOS library.
Following
> the MET tutorial, I performed all the steps except the last one (cp
> include/*.h ../../include/.). At the point where I am supposed to
> execute this statement, I am sitting in the following directory:
>
> /p/home/jraby/hdfeos/hdfeos
>
> If I execute the cp statement as is, it looks for the target dir up
in
> my home
> (jraby) and there is no "include" dir in jraby. I need more info as
to
> what the intended destination is or where the target dir is supposed
> to be located so I can modify the path I use accordingly.
>
> Thanks.
>
> R/
> John
>
> -----Original Message-----
> From: Julie Prestopnik via RT [Caution-mailto:met_help at ucar.edu]
> Sent: Monday, January 09, 2017 10:49 AM
> To: Raby, John W CIV USARMY RDECOM ARL (US)
> <john.w.raby2.civ at mail.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
> about compiling GRIB2 C-Library (UNCLASSIFIED)
>
> All active links contained in this email were disabled. Please
verify
> the identity of the sender, and confirm the authenticity of all
links
> contained within the message prior to copying and pasting the
address
> to a Web browser.
>
>
>
>
> ----
>
> Hi John.
>
> I see that you have some questions regarding compiling the GRIB2C
library.
> Instead of the following:
>
> INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
>
> You'll want to have:
>
> INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> -I/p/home/jraby/PNG/libpng-1.2.34/include/
-I/p/home/jraby/zlib/zlib-
> 1.2.8/include/
>
> Please note that the -I and paths that follow are separated by
spaces.
> If you keep what you have currently, I believe that it will only
> include the last one (zlib).
>
> I see now that for the GRIB2C library, the setting of CFLAGS is done
> inside the makefile. That should work for compiling GRIB2C,
however,
> for MET you'll need to set the environment variable "CFLAGS" to
> include "
> -D__64BIT__" using export.
>
> Your change:
>
> #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in
the
> original makefile.
> # The following line names the library to the same name as that
> expected by MET per the guidance from the MET User's Guide and the
MET
> tutorial.
> LIB=libgrib2c.a
>
> looks correct to me.
>
> Give that a try. Hopefully, everything will go smoothly. Please
let
> us know if you encounter any other troubles.
>
> Thanks!
>
> Julie
>
> On Mon, Jan 9, 2017 at 9:42 AM, Raby, John W USA CIV via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <Caution-Caution-url:
> > Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79
> > 100 >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> > Julie -
> >
> > I edited the makefile (attached as a wordpad file) as follows to
> > accomplish the changes we discussed last week:
> >
> > #INC=-I/nwprod/lib/include/-->in original makefile.
> >
> > # The following INC settings were added by John Raby per the
> > guidance provided by Julie Prestopnik from the MET Help Desk:
> > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> > INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> > #
> > # This "C" source code contains many uses of the C++
> > # comment style "//". Please make sure you include the
> > # appropriate compiler flag to allow the use of "//" comment
> indicators.
> > #
> >
> > # The following line sets the option for 64-bit.
> > CFLAGS= -O3 -g -m64 $(INC) $(DEFS) -D__64BIT__
> >
> > CC=gcc
> >
> > #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in
> > the original makefile.
> > # The following line names the library to the same name as that
> > expected by MET per the guidance from the MET User's Guide and the
> > MET tutorial.
> > LIB=libgrib2c.a
> >
> > ************************************************************
> > **********************************************************
> >
> > Some comments about the edit changes:
> >
> > I commented out the original INC statement and added 3 INC
> > statements to account for jasper, zlib and PNG. I assume that
> > multiple INC statements to do this will work, but I've never done
> > this before. Not sure if you can re-use INC for different paths or
> > whether you have to use INC1, INC2, ....INCX??
> >
> > It looked like the option for 64-bit is specified in the makefile
> > rather than using "export". Will this work?
> >
> > I commented out the original statement " LIB=libg2c_v1.6.0.a" and
> > added a new one to name the library as expected by MET.
> >
> > Could you review my changes to see if they are correct?
> >
> > Thanks.
> >
> > R/
> > John
> >
> >
> > -----Original Message-----
> > From: Julie Prestopnik via RT
> > [Caution-Caution-mailto:met_help at ucar.edu]
> > Sent: Friday, January 06, 2017 2:21 PM
> > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > <john.w.raby2.civ at mail.mil>
> > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
> > about compiling GRIB2 C-Library (UNCLASSIFIED)
> >
> > All active links contained in this email were disabled. Please
> > verify the identity of the sender, and confirm the authenticity of
> > all links contained within the message prior to copying and
pasting
> > the address to a Web browser.
> >
> >
> >
> >
> > ----
> >
> > Hi John.
> >
> > Support for GRIB2 is disabled by default in MET. However, since
you
> > would like support for GRIB2 files you will need to compile the
> > GRIB2C Library and enable GRIB2 support when configuring MET with"
> > *--enable-grib2*".
> >
> > I believe you would want to use the 64 bit flag if you were
running
> > on a 64 bit machine. You would do that by setting
> > *CFLAGS="-D__64BIT__"*, either with setenv or with export (for
bash).
> > You just need to make sure that if you configure the GRIB2C
library
> > in this way, you also configure MET in this way.
> > Compiling MET and the GRIB2C library inconsistently may result in
a
> > segmentation fault when reading GRIB2 files.
> >
> > To compile the GRIB2C library, please do the following:
> >
> > # Get the GRIB2C library
> > wget
> > Caution-Caution-Caution-
http://www.nco.ncep.noaa.gov/pmb/codes/GRIB2
> > /
> > g2clib-1.6.0.tar
> >
> > # Untar it
> > tar -xvf g2clib-1.6.0.tar
> > cd g2clib-1.6.0
> >
> > # Open up and edit the "makefile"
> > # Set INC =-I/path/for/include/files
> > # Please make sure to include all idirectories where include
files
> > # can be found (jasper/*.h and png.h pngconf.h zconf.h
zlib.h)
> >
> > # Compile it
> > make
> >
> > I hope that helps!
> >
> > Julie
> >
> >
> > On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> > > Transaction: Ticket created by john.w.raby2.civ at mail.mil
> > > Queue: met_help
> > > Subject: question about compiling GRIB2 C-Library
(UNCLASSIFIED)
> > > Owner: Nobody
> > > Requestors: john.w.raby2.civ at mail.mil
> > > Status: new
> > > Ticket <Caution-Caution-Caution-url:
> > > Caution-Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.
> > > html?id=79
> > > 100 >
> > >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > > Unlike zlib, png and jasper which involved the running of
> > > ./configure before running make, unpacking of g2clib failed to
> > > produce a configure script. The README which was produced
doesn't
> > > seem to provide much info about running ./configure. Is this a
> > > problem? The MET tutorial and User's Guide describe some
specific
> > > requirement for compiling with or without the option -D__64BIT,
> > > but it is not clear how this option is specified. Could you
> > > clarify on this issue? Also, what are the considerations which
> > > would help the user choose between a configuration with the
> > > D__64BIT option vs a configuration without it.
> > > I am progressing with installing MET V5.2 and would like GRIB2
> > > support.
> > >
> > > Thanks.
> > >
> > > R/
> > > John
> > >
> > > Mr John W. Raby, Meteorologist
> > > U.S. Army Research Laboratory
> > > White Sands Missile Range, NM 88002
> > > (575) 678-2004 DSN 258-2004
> > > FAX (575) 678-1230 DSN 258-1230
> > > Email: john.w.raby2.civ at mail.mil
> > >
> > >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > >
> >
> >
> > --
> > Julie Prestopnik
> > National Center for Atmospheric Research Research Applications
> > Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> >
>
>
> --
> Julie Prestopnik
> National Center for Atmospheric Research Research Applications
> Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research Research Applications
Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
CLASSIFICATION: UNCLASSIFIED
------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Julie Prestopnik
Time: Wed Jan 11 10:19:18 2017
Hi John. There is no need to run "make install" (and in fact we can't
because there is "No rule to make target 'install'." for this
library).
When you get to:
http://www.dtcenter.org/met/users/support/online_tutorial/METv5.2/tutorial.php?name=compilation&category=configure
you'll see that it says:
"If compiling support for *GRIB2*, set *$MET_GRIB2CINC* and
*$MET_GRIB2CLIB*
to point to the main GRIB2C directory which contains both the include
and
library files. These are used instead of *$MET_GRIB2C* since the main
GRIB2C directory does not contain include and lib subdirectories."
So you can just set these environment variables to point to the main
GRIB2C
directory and MET should compile well.
Julie
On Tue, Jan 10, 2017 at 3:52 PM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
> CLASSIFICATION: UNCLASSIFIED
>
> Julie -
>
> Regards the compiling of the GRIB2C library, I sent an email earlier
today
> which mentioned that after I edited the makefile to change "gcc" to
"icc"
> per
> your suggestion, I was able to run "make" and no messages about
"linking
> not
> done" appeared.
>
> I went ahead and ran "make install" in the following location
> (${INSTALL_DIR))
> or /p/home/jraby/grib2c/g2clib-1.6.0, but it was stopped with the
> following
> error:
>
> > make install
> make: *** No rule to make target `install'. Stop.
> excalibur:~jraby/grib2c/g2clib-1.6.0
>
> I'm not sure what the problem is.
>
> R/
> John
>
>
> -----Original Message-----
> From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, January 10, 2017 9:23 AM
> To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about
> compiling GRIB2 C-Library (UNCLASSIFIED)
>
> All active links contained in this email were disabled. Please
verify the
> identity of the sender, and confirm the authenticity of all links
contained
> within the message prior to copying and pasting the address to a Web
> browser.
>
>
>
>
> ----
>
> Hi John.
>
> I see you have a question about the message " linker input file
unused
> because
> linking not done". I think that may indicate a problem which would
need
> to be
> fixed before the install.
>
> The statement "CC=gcc" does this refer to the value of the common
> environment
> variable $CC which you said for your system is "icc". Please change
that
> value in the makefile for the GRIB2C library. The same family of
compilers
> should be used to build all of the external libraries and MET.
Mixing GNU
> compilers with Intel compilers is not a good idea.
>
> Please change that "gcc" value to "icc" in the makefile and try it
again.
> Please let me know if that makes those messages go away.
>
> Regarding your question about copying over the header files for the
HDF-EOS
> libraries, I believe you want to copy them over the include
directory in
> your
> *${INSTALL_DIR}*. Please give that a try and let us know if you
experience
> any problems. In the meantime, I'll work on clarifying why it
currently
> says
> "cp include/*.h ../../include/".
>
> Thanks,
> Julie
>
> On Mon, Jan 9, 2017 at 2:49 PM, Raby, John W USA CIV via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <Caution-url:
> > Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> > Julie -
> >
> > I edited the makefile to incorporate the changes. Then on running
make
> > I noticed a potential issue which appeared in the screen dialog.
The
> > following statement appeared numerous times:
> >
> > gcc: /p/home/jraby/PNG/libpng-1.2.34/include: linker input file
unused
> > because linking not done
> > gcc: /p/home/jraby/zlib/zlib-1.2.8/include: linker input file
unused
> > because linking not done ar -ruv libgrib2c.a seekgb.o a -
seekgb.o rm
> > -f seekgb.o
> > excalibur:~jraby/grib2c/g2clib-1.6.0
> >
> > Does this indicate a problem which needs to be fixed before the
install?
> >
> > I have one question which occurred to me as I was editing the
> > makefile. I noticed that there is s statement "CC=gcc". Does this
> > refer to the value of the common environment variable $CC which
for my
> > system (Excalibur) is "icc"
> > not "gcc". Maybe this is no issue at all, but I wanted to ask you
> > about it in case it is.
> >
> > I also have a question about compiling the HDF-EOS library.
Following
> > the MET tutorial, I performed all the steps except the last one
(cp
> > include/*.h ../../include/.). At the point where I am supposed to
> > execute this statement, I am sitting in the following directory:
> >
> > /p/home/jraby/hdfeos/hdfeos
> >
> > If I execute the cp statement as is, it looks for the target dir
up in
> > my home
> > (jraby) and there is no "include" dir in jraby. I need more info
as to
> > what the intended destination is or where the target dir is
supposed
> > to be located so I can modify the path I use accordingly.
> >
> > Thanks.
> >
> > R/
> > John
> >
> > -----Original Message-----
> > From: Julie Prestopnik via RT [Caution-mailto:met_help at ucar.edu]
> > Sent: Monday, January 09, 2017 10:49 AM
> > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > <john.w.raby2.civ at mail.mil>
> > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100]
question
> > about compiling GRIB2 C-Library (UNCLASSIFIED)
> >
> > All active links contained in this email were disabled. Please
verify
> > the identity of the sender, and confirm the authenticity of all
links
> > contained within the message prior to copying and pasting the
address
> > to a Web browser.
> >
> >
> >
> >
> > ----
> >
> > Hi John.
> >
> > I see that you have some questions regarding compiling the GRIB2C
> library.
> > Instead of the following:
> >
> > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> > INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> >
> > You'll want to have:
> >
> > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > -I/p/home/jraby/PNG/libpng-1.2.34/include/
-I/p/home/jraby/zlib/zlib-
> > 1.2.8/include/
> >
> > Please note that the -I and paths that follow are separated by
spaces.
> > If you keep what you have currently, I believe that it will only
> > include the last one (zlib).
> >
> > I see now that for the GRIB2C library, the setting of CFLAGS is
done
> > inside the makefile. That should work for compiling GRIB2C,
however,
> > for MET you'll need to set the environment variable "CFLAGS" to
> > include "
> > -D__64BIT__" using export.
> >
> > Your change:
> >
> > #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in
the
> > original makefile.
> > # The following line names the library to the same name as that
> > expected by MET per the guidance from the MET User's Guide and the
MET
> > tutorial.
> > LIB=libgrib2c.a
> >
> > looks correct to me.
> >
> > Give that a try. Hopefully, everything will go smoothly. Please
let
> > us know if you encounter any other troubles.
> >
> > Thanks!
> >
> > Julie
> >
> > On Mon, Jan 9, 2017 at 9:42 AM, Raby, John W USA CIV via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <Caution-Caution-url:
> > > Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79
> > > 100 >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > > Julie -
> > >
> > > I edited the makefile (attached as a wordpad file) as follows to
> > > accomplish the changes we discussed last week:
> > >
> > > #INC=-I/nwprod/lib/include/-->in original makefile.
> > >
> > > # The following INC settings were added by John Raby per the
> > > guidance provided by Julie Prestopnik from the MET Help Desk:
> > > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > > INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> > > INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> > > #
> > > # This "C" source code contains many uses of the C++
> > > # comment style "//". Please make sure you include the
> > > # appropriate compiler flag to allow the use of "//" comment
> > indicators.
> > > #
> > >
> > > # The following line sets the option for 64-bit.
> > > CFLAGS= -O3 -g -m64 $(INC) $(DEFS) -D__64BIT__
> > >
> > > CC=gcc
> > >
> > > #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library
in
> > > the original makefile.
> > > # The following line names the library to the same name as that
> > > expected by MET per the guidance from the MET User's Guide and
the
> > > MET tutorial.
> > > LIB=libgrib2c.a
> > >
> > > ************************************************************
> > > **********************************************************
> > >
> > > Some comments about the edit changes:
> > >
> > > I commented out the original INC statement and added 3 INC
> > > statements to account for jasper, zlib and PNG. I assume that
> > > multiple INC statements to do this will work, but I've never
done
> > > this before. Not sure if you can re-use INC for different paths
or
> > > whether you have to use INC1, INC2, ....INCX??
> > >
> > > It looked like the option for 64-bit is specified in the
makefile
> > > rather than using "export". Will this work?
> > >
> > > I commented out the original statement " LIB=libg2c_v1.6.0.a"
and
> > > added a new one to name the library as expected by MET.
> > >
> > > Could you review my changes to see if they are correct?
> > >
> > > Thanks.
> > >
> > > R/
> > > John
> > >
> > >
> > > -----Original Message-----
> > > From: Julie Prestopnik via RT
> > > [Caution-Caution-mailto:met_help at ucar.edu]
> > > Sent: Friday, January 06, 2017 2:21 PM
> > > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > > <john.w.raby2.civ at mail.mil>
> > > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
> > > about compiling GRIB2 C-Library (UNCLASSIFIED)
> > >
> > > All active links contained in this email were disabled. Please
> > > verify the identity of the sender, and confirm the authenticity
of
> > > all links contained within the message prior to copying and
pasting
> > > the address to a Web browser.
> > >
> > >
> > >
> > >
> > > ----
> > >
> > > Hi John.
> > >
> > > Support for GRIB2 is disabled by default in MET. However, since
you
> > > would like support for GRIB2 files you will need to compile the
> > > GRIB2C Library and enable GRIB2 support when configuring MET
with"
> > > *--enable-grib2*".
> > >
> > > I believe you would want to use the 64 bit flag if you were
running
> > > on a 64 bit machine. You would do that by setting
> > > *CFLAGS="-D__64BIT__"*, either with setenv or with export (for
bash).
> > > You just need to make sure that if you configure the GRIB2C
library
> > > in this way, you also configure MET in this way.
> > > Compiling MET and the GRIB2C library inconsistently may result
in a
> > > segmentation fault when reading GRIB2 files.
> > >
> > > To compile the GRIB2C library, please do the following:
> > >
> > > # Get the GRIB2C library
> > > wget
> > > Caution-Caution-Caution-
http://www.nco.ncep.noaa.gov/pmb/codes/GRIB2
> > > /
> > > g2clib-1.6.0.tar
> > >
> > > # Untar it
> > > tar -xvf g2clib-1.6.0.tar
> > > cd g2clib-1.6.0
> > >
> > > # Open up and edit the "makefile"
> > > # Set INC =-I/path/for/include/files
> > > # Please make sure to include all idirectories where include
files
> > > # can be found (jasper/*.h and png.h pngconf.h zconf.h
zlib.h)
> > >
> > > # Compile it
> > > make
> > >
> > > I hope that helps!
> > >
> > > Julie
> > >
> > >
> > > On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> > > > Transaction: Ticket created by john.w.raby2.civ at mail.mil
> > > > Queue: met_help
> > > > Subject: question about compiling GRIB2 C-Library
(UNCLASSIFIED)
> > > > Owner: Nobody
> > > > Requestors: john.w.raby2.civ at mail.mil
> > > > Status: new
> > > > Ticket <Caution-Caution-Caution-url:
> > > > Caution-Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.
> > > > html?id=79
> > > > 100 >
> > > >
> > > >
> > > > CLASSIFICATION: UNCLASSIFIED
> > > >
> > > > Unlike zlib, png and jasper which involved the running of
> > > > ./configure before running make, unpacking of g2clib failed to
> > > > produce a configure script. The README which was produced
doesn't
> > > > seem to provide much info about running ./configure. Is this a
> > > > problem? The MET tutorial and User's Guide describe some
specific
> > > > requirement for compiling with or without the option
-D__64BIT,
> > > > but it is not clear how this option is specified. Could you
> > > > clarify on this issue? Also, what are the considerations which
> > > > would help the user choose between a configuration with the
> > > > D__64BIT option vs a configuration without it.
> > > > I am progressing with installing MET V5.2 and would like GRIB2
> > > > support.
> > > >
> > > > Thanks.
> > > >
> > > > R/
> > > > John
> > > >
> > > > Mr John W. Raby, Meteorologist
> > > > U.S. Army Research Laboratory
> > > > White Sands Missile Range, NM 88002
> > > > (575) 678-2004 DSN 258-2004
> > > > FAX (575) 678-1230 DSN 258-1230
> > > > Email: john.w.raby2.civ at mail.mil
> > > >
> > > >
> > > >
> > > > CLASSIFICATION: UNCLASSIFIED
> > > >
> > > >
> > >
> > >
> > > --
> > > Julie Prestopnik
> > > National Center for Atmospheric Research Research Applications
> > > Laboratory
> > > Phone: 303.497.8399
> > > Email: jpresto at ucar.edu
> > >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > >
> >
> >
> > --
> > Julie Prestopnik
> > National Center for Atmospheric Research Research Applications
> > Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> >
>
>
> --
> Julie Prestopnik
> National Center for Atmospheric Research Research Applications
Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Wed Jan 11 12:49:57 2017
CLASSIFICATION: UNCLASSIFIED
Julie -
Thanks for your response.
I looked at my main GRIB2C directory which contains the following two
items:
excalibur:~jraby/grib2c
> ls
g2clib-1.6.0/ g2clib-1.6.0.tar
excalibur:~jraby/grib2c
The subdirectory g2clib-1.6.0 does not contain include or library
directories.
R/
John
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, January 11, 2017 10:19 AM
To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about
compiling GRIB2 C-Library (UNCLASSIFIED)
All active links contained in this email were disabled. Please verify
the
identity of the sender, and confirm the authenticity of all links
contained
within the message prior to copying and pasting the address to a Web
browser.
----
Hi John. There is no need to run "make install" (and in fact we can't
because
there is "No rule to make target 'install'." for this library).
When you get to:
Caution-
http://www.dtcenter.org/met/users/support/online_tutorial/METv5.2/tutorial.php?name=compilation&category=configure
you'll see that it says:
"If compiling support for *GRIB2*, set *$MET_GRIB2CINC* and
*$MET_GRIB2CLIB*
to point to the main GRIB2C directory which contains both the include
and
library files. These are used instead of *$MET_GRIB2C* since the main
GRIB2C
directory does not contain include and lib subdirectories."
So you can just set these environment variables to point to the main
GRIB2C
directory and MET should compile well.
Julie
On Tue, Jan 10, 2017 at 3:52 PM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> <Caution-url:
> Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
> CLASSIFICATION: UNCLASSIFIED
>
> Julie -
>
> Regards the compiling of the GRIB2C library, I sent an email earlier
> today which mentioned that after I edited the makefile to change
"gcc" to
> "icc"
> per
> your suggestion, I was able to run "make" and no messages about
> "linking not done" appeared.
>
> I went ahead and ran "make install" in the following location
> (${INSTALL_DIR))
> or /p/home/jraby/grib2c/g2clib-1.6.0, but it was stopped with the
> following
> error:
>
> > make install
> make: *** No rule to make target `install'. Stop.
> excalibur:~jraby/grib2c/g2clib-1.6.0
>
> I'm not sure what the problem is.
>
> R/
> John
>
>
> -----Original Message-----
> From: Julie Prestopnik via RT [Caution-mailto:met_help at ucar.edu]
> Sent: Tuesday, January 10, 2017 9:23 AM
> To: Raby, John W CIV USARMY RDECOM ARL (US)
> <john.w.raby2.civ at mail.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
> about compiling GRIB2 C-Library (UNCLASSIFIED)
>
> All active links contained in this email were disabled. Please
verify
> the identity of the sender, and confirm the authenticity of all
links
> contained within the message prior to copying and pasting the
address
> to a Web browser.
>
>
>
>
> ----
>
> Hi John.
>
> I see you have a question about the message " linker input file
unused
> because linking not done". I think that may indicate a problem
which
> would need to be fixed before the install.
>
> The statement "CC=gcc" does this refer to the value of the common
> environment variable $CC which you said for your system is "icc".
> Please change that value in the makefile for the GRIB2C library.
The
> same family of compilers should be used to build all of the external
> libraries and MET. Mixing GNU compilers with Intel compilers is not
a
> good idea.
>
> Please change that "gcc" value to "icc" in the makefile and try it
again.
> Please let me know if that makes those messages go away.
>
> Regarding your question about copying over the header files for the
> HDF-EOS libraries, I believe you want to copy them over the include
> directory in your *${INSTALL_DIR}*. Please give that a try and let
us
> know if you experience any problems. In the meantime, I'll work on
> clarifying why it currently says "cp include/*.h ../../include/".
>
> Thanks,
> Julie
>
> On Mon, Jan 9, 2017 at 2:49 PM, Raby, John W USA CIV via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <Caution-Caution-url:
> > Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79
> > 100 >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> > Julie -
> >
> > I edited the makefile to incorporate the changes. Then on running
> > make I noticed a potential issue which appeared in the screen
> > dialog. The following statement appeared numerous times:
> >
> > gcc: /p/home/jraby/PNG/libpng-1.2.34/include: linker input file
> > unused because linking not done
> > gcc: /p/home/jraby/zlib/zlib-1.2.8/include: linker input file
unused
> > because linking not done ar -ruv libgrib2c.a seekgb.o a -
seekgb.o
> > rm -f seekgb.o
> > excalibur:~jraby/grib2c/g2clib-1.6.0
> >
> > Does this indicate a problem which needs to be fixed before the
install?
> >
> > I have one question which occurred to me as I was editing the
> > makefile. I noticed that there is s statement "CC=gcc". Does this
> > refer to the value of the common environment variable $CC which
for
> > my system (Excalibur) is "icc"
> > not "gcc". Maybe this is no issue at all, but I wanted to ask you
> > about it in case it is.
> >
> > I also have a question about compiling the HDF-EOS library.
> > Following the MET tutorial, I performed all the steps except the
> > last one (cp include/*.h ../../include/.). At the point where I am
> > supposed to execute this statement, I am sitting in the following
> > directory:
> >
> > /p/home/jraby/hdfeos/hdfeos
> >
> > If I execute the cp statement as is, it looks for the target dir
up
> > in my home
> > (jraby) and there is no "include" dir in jraby. I need more info
as
> > to what the intended destination is or where the target dir is
> > supposed to be located so I can modify the path I use accordingly.
> >
> > Thanks.
> >
> > R/
> > John
> >
> > -----Original Message-----
> > From: Julie Prestopnik via RT
> > [Caution-Caution-mailto:met_help at ucar.edu]
> > Sent: Monday, January 09, 2017 10:49 AM
> > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > <john.w.raby2.civ at mail.mil>
> > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100]
question
> > about compiling GRIB2 C-Library (UNCLASSIFIED)
> >
> > All active links contained in this email were disabled. Please
> > verify the identity of the sender, and confirm the authenticity of
> > all links contained within the message prior to copying and
pasting
> > the address to a Web browser.
> >
> >
> >
> >
> > ----
> >
> > Hi John.
> >
> > I see that you have some questions regarding compiling the GRIB2C
> library.
> > Instead of the following:
> >
> > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> > INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> >
> > You'll want to have:
> >
> > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > -I/p/home/jraby/PNG/libpng-1.2.34/include/
> > -I/p/home/jraby/zlib/zlib- 1.2.8/include/
> >
> > Please note that the -I and paths that follow are separated by
spaces.
> > If you keep what you have currently, I believe that it will only
> > include the last one (zlib).
> >
> > I see now that for the GRIB2C library, the setting of CFLAGS is
done
> > inside the makefile. That should work for compiling GRIB2C,
> > however, for MET you'll need to set the environment variable
> > "CFLAGS" to include "
> > -D__64BIT__" using export.
> >
> > Your change:
> >
> > #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in
> > the original makefile.
> > # The following line names the library to the same name as that
> > expected by MET per the guidance from the MET User's Guide and the
> > MET tutorial.
> > LIB=libgrib2c.a
> >
> > looks correct to me.
> >
> > Give that a try. Hopefully, everything will go smoothly. Please
> > let us know if you encounter any other troubles.
> >
> > Thanks!
> >
> > Julie
> >
> > On Mon, Jan 9, 2017 at 9:42 AM, Raby, John W USA CIV via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <Caution-Caution-Caution-url:
> > > Caution-Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.
> > > html?id=79
> > > 100 >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > > Julie -
> > >
> > > I edited the makefile (attached as a wordpad file) as follows to
> > > accomplish the changes we discussed last week:
> > >
> > > #INC=-I/nwprod/lib/include/-->in original makefile.
> > >
> > > # The following INC settings were added by John Raby per the
> > > guidance provided by Julie Prestopnik from the MET Help Desk:
> > > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > > INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> > > INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> > > #
> > > # This "C" source code contains many uses of the C++
> > > # comment style "//". Please make sure you include the
> > > # appropriate compiler flag to allow the use of "//" comment
> > indicators.
> > > #
> > >
> > > # The following line sets the option for 64-bit.
> > > CFLAGS= -O3 -g -m64 $(INC) $(DEFS) -D__64BIT__
> > >
> > > CC=gcc
> > >
> > > #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library
in
> > > the original makefile.
> > > # The following line names the library to the same name as that
> > > expected by MET per the guidance from the MET User's Guide and
the
> > > MET tutorial.
> > > LIB=libgrib2c.a
> > >
> > > ************************************************************
> > > **********************************************************
> > >
> > > Some comments about the edit changes:
> > >
> > > I commented out the original INC statement and added 3 INC
> > > statements to account for jasper, zlib and PNG. I assume that
> > > multiple INC statements to do this will work, but I've never
done
> > > this before. Not sure if you can re-use INC for different paths
or
> > > whether you have to use INC1, INC2, ....INCX??
> > >
> > > It looked like the option for 64-bit is specified in the
makefile
> > > rather than using "export". Will this work?
> > >
> > > I commented out the original statement " LIB=libg2c_v1.6.0.a"
and
> > > added a new one to name the library as expected by MET.
> > >
> > > Could you review my changes to see if they are correct?
> > >
> > > Thanks.
> > >
> > > R/
> > > John
> > >
> > >
> > > -----Original Message-----
> > > From: Julie Prestopnik via RT
> > > [Caution-Caution-Caution-mailto:met_help at ucar.edu]
> > > Sent: Friday, January 06, 2017 2:21 PM
> > > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > > <john.w.raby2.civ at mail.mil>
> > > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
> > > about compiling GRIB2 C-Library (UNCLASSIFIED)
> > >
> > > All active links contained in this email were disabled. Please
> > > verify the identity of the sender, and confirm the authenticity
of
> > > all links contained within the message prior to copying and
> > > pasting the address to a Web browser.
> > >
> > >
> > >
> > >
> > > ----
> > >
> > > Hi John.
> > >
> > > Support for GRIB2 is disabled by default in MET. However, since
> > > you would like support for GRIB2 files you will need to compile
> > > the GRIB2C Library and enable GRIB2 support when configuring MET
with"
> > > *--enable-grib2*".
> > >
> > > I believe you would want to use the 64 bit flag if you were
> > > running on a 64 bit machine. You would do that by setting
> > > *CFLAGS="-D__64BIT__"*, either with setenv or with export (for
bash).
> > > You just need to make sure that if you configure the GRIB2C
> > > library in this way, you also configure MET in this way.
> > > Compiling MET and the GRIB2C library inconsistently may result
in
> > > a segmentation fault when reading GRIB2 files.
> > >
> > > To compile the GRIB2C library, please do the following:
> > >
> > > # Get the GRIB2C library
> > > wget
> > > Caution-Caution-Caution-Caution-
http://www.nco.ncep.noaa.gov/pmb/c
> > > odes/GRIB2
> > > /
> > > g2clib-1.6.0.tar
> > >
> > > # Untar it
> > > tar -xvf g2clib-1.6.0.tar
> > > cd g2clib-1.6.0
> > >
> > > # Open up and edit the "makefile"
> > > # Set INC =-I/path/for/include/files
> > > # Please make sure to include all idirectories where include
files
> > > # can be found (jasper/*.h and png.h pngconf.h zconf.h
zlib.h)
> > >
> > > # Compile it
> > > make
> > >
> > > I hope that helps!
> > >
> > > Julie
> > >
> > >
> > > On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> > > > Transaction: Ticket created by john.w.raby2.civ at mail.mil
> > > > Queue: met_help
> > > > Subject: question about compiling GRIB2 C-Library
(UNCLASSIFIED)
> > > > Owner: Nobody
> > > > Requestors: john.w.raby2.civ at mail.mil
> > > > Status: new
> > > > Ticket <Caution-Caution-Caution-Caution-url:
> > > > Caution-Caution-Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.
> > > > html?id=79
> > > > 100 >
> > > >
> > > >
> > > > CLASSIFICATION: UNCLASSIFIED
> > > >
> > > > Unlike zlib, png and jasper which involved the running of
> > > > ./configure before running make, unpacking of g2clib failed to
> > > > produce a configure script. The README which was produced
> > > > doesn't seem to provide much info about running ./configure.
Is
> > > > this a problem? The MET tutorial and User's Guide describe
some
> > > > specific requirement for compiling with or without the option
> > > > -D__64BIT, but it is not clear how this option is specified.
> > > > Could you clarify on this issue? Also, what are the
> > > > considerations which would help the user choose between a
> > > > configuration with the D__64BIT option vs a configuration
without it.
> > > > I am progressing with installing MET V5.2 and would like GRIB2
> > > > support.
> > > >
> > > > Thanks.
> > > >
> > > > R/
> > > > John
> > > >
> > > > Mr John W. Raby, Meteorologist
> > > > U.S. Army Research Laboratory
> > > > White Sands Missile Range, NM 88002
> > > > (575) 678-2004 DSN 258-2004
> > > > FAX (575) 678-1230 DSN 258-1230
> > > > Email: john.w.raby2.civ at mail.mil
> > > >
> > > >
> > > >
> > > > CLASSIFICATION: UNCLASSIFIED
> > > >
> > > >
> > >
> > >
> > > --
> > > Julie Prestopnik
> > > National Center for Atmospheric Research Research Applications
> > > Laboratory
> > > Phone: 303.497.8399
> > > Email: jpresto at ucar.edu
> > >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > >
> >
> >
> > --
> > Julie Prestopnik
> > National Center for Atmospheric Research Research Applications
> > Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> >
>
>
> --
> Julie Prestopnik
> National Center for Atmospheric Research Research Applications
> Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research Research Applications
Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
CLASSIFICATION: UNCLASSIFIED
------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Wed Jan 11 13:23:56 2017
CLASSIFICATION: UNCLASSIFIED
Julie -
I read the tutorial page at
http://www.dtcenter.org/met/users/support/online_tutorial/METv5.2/tutorial.php?name=compilation&category=req_libs
The section on GRIB2C mentions that the required library, called
libgrib2c.a,
is what MET will look for and that. I checked the contents of my dir
g2clib-1.6.0 and it contains libgrib2c.a. So when I compile MET for
GRIB2
support, I should use the two environment variables and point them to
the dir
which contains libgrib2c.a.
What's confusing for me is that at the page your provided the link
for, they
state that you should point to the dir containing the "include" and
"library"
files, but in the page above they explicitly mention the dir which
contains
libgrib2c.a. Maybe they are saying the same thing?
What's your take?
R/
John
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, January 11, 2017 10:19 AM
To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about
compiling GRIB2 C-Library (UNCLASSIFIED)
All active links contained in this email were disabled. Please verify
the
identity of the sender, and confirm the authenticity of all links
contained
within the message prior to copying and pasting the address to a Web
browser.
----
Hi John. There is no need to run "make install" (and in fact we can't
because
there is "No rule to make target 'install'." for this library).
When you get to:
Caution-
http://www.dtcenter.org/met/users/support/online_tutorial/METv5.2/tutorial.php?name=compilation&category=configure
you'll see that it says:
"If compiling support for *GRIB2*, set *$MET_GRIB2CINC* and
*$MET_GRIB2CLIB*
to point to the main GRIB2C directory which contains both the include
and
library files. These are used instead of *$MET_GRIB2C* since the main
GRIB2C
directory does not contain include and lib subdirectories."
So you can just set these environment variables to point to the main
GRIB2C
directory and MET should compile well.
Julie
On Tue, Jan 10, 2017 at 3:52 PM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> <Caution-url:
> Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
> CLASSIFICATION: UNCLASSIFIED
>
> Julie -
>
> Regards the compiling of the GRIB2C library, I sent an email earlier
> today which mentioned that after I edited the makefile to change
"gcc" to
> "icc"
> per
> your suggestion, I was able to run "make" and no messages about
> "linking not done" appeared.
>
> I went ahead and ran "make install" in the following location
> (${INSTALL_DIR))
> or /p/home/jraby/grib2c/g2clib-1.6.0, but it was stopped with the
> following
> error:
>
> > make install
> make: *** No rule to make target `install'. Stop.
> excalibur:~jraby/grib2c/g2clib-1.6.0
>
> I'm not sure what the problem is.
>
> R/
> John
>
>
> -----Original Message-----
> From: Julie Prestopnik via RT [Caution-mailto:met_help at ucar.edu]
> Sent: Tuesday, January 10, 2017 9:23 AM
> To: Raby, John W CIV USARMY RDECOM ARL (US)
> <john.w.raby2.civ at mail.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
> about compiling GRIB2 C-Library (UNCLASSIFIED)
>
> All active links contained in this email were disabled. Please
verify
> the identity of the sender, and confirm the authenticity of all
links
> contained within the message prior to copying and pasting the
address
> to a Web browser.
>
>
>
>
> ----
>
> Hi John.
>
> I see you have a question about the message " linker input file
unused
> because linking not done". I think that may indicate a problem
which
> would need to be fixed before the install.
>
> The statement "CC=gcc" does this refer to the value of the common
> environment variable $CC which you said for your system is "icc".
> Please change that value in the makefile for the GRIB2C library.
The
> same family of compilers should be used to build all of the external
> libraries and MET. Mixing GNU compilers with Intel compilers is not
a
> good idea.
>
> Please change that "gcc" value to "icc" in the makefile and try it
again.
> Please let me know if that makes those messages go away.
>
> Regarding your question about copying over the header files for the
> HDF-EOS libraries, I believe you want to copy them over the include
> directory in your *${INSTALL_DIR}*. Please give that a try and let
us
> know if you experience any problems. In the meantime, I'll work on
> clarifying why it currently says "cp include/*.h ../../include/".
>
> Thanks,
> Julie
>
> On Mon, Jan 9, 2017 at 2:49 PM, Raby, John W USA CIV via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <Caution-Caution-url:
> > Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79
> > 100 >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> > Julie -
> >
> > I edited the makefile to incorporate the changes. Then on running
> > make I noticed a potential issue which appeared in the screen
> > dialog. The following statement appeared numerous times:
> >
> > gcc: /p/home/jraby/PNG/libpng-1.2.34/include: linker input file
> > unused because linking not done
> > gcc: /p/home/jraby/zlib/zlib-1.2.8/include: linker input file
unused
> > because linking not done ar -ruv libgrib2c.a seekgb.o a -
seekgb.o
> > rm -f seekgb.o
> > excalibur:~jraby/grib2c/g2clib-1.6.0
> >
> > Does this indicate a problem which needs to be fixed before the
install?
> >
> > I have one question which occurred to me as I was editing the
> > makefile. I noticed that there is s statement "CC=gcc". Does this
> > refer to the value of the common environment variable $CC which
for
> > my system (Excalibur) is "icc"
> > not "gcc". Maybe this is no issue at all, but I wanted to ask you
> > about it in case it is.
> >
> > I also have a question about compiling the HDF-EOS library.
> > Following the MET tutorial, I performed all the steps except the
> > last one (cp include/*.h ../../include/.). At the point where I am
> > supposed to execute this statement, I am sitting in the following
> > directory:
> >
> > /p/home/jraby/hdfeos/hdfeos
> >
> > If I execute the cp statement as is, it looks for the target dir
up
> > in my home
> > (jraby) and there is no "include" dir in jraby. I need more info
as
> > to what the intended destination is or where the target dir is
> > supposed to be located so I can modify the path I use accordingly.
> >
> > Thanks.
> >
> > R/
> > John
> >
> > -----Original Message-----
> > From: Julie Prestopnik via RT
> > [Caution-Caution-mailto:met_help at ucar.edu]
> > Sent: Monday, January 09, 2017 10:49 AM
> > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > <john.w.raby2.civ at mail.mil>
> > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100]
question
> > about compiling GRIB2 C-Library (UNCLASSIFIED)
> >
> > All active links contained in this email were disabled. Please
> > verify the identity of the sender, and confirm the authenticity of
> > all links contained within the message prior to copying and
pasting
> > the address to a Web browser.
> >
> >
> >
> >
> > ----
> >
> > Hi John.
> >
> > I see that you have some questions regarding compiling the GRIB2C
> library.
> > Instead of the following:
> >
> > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> > INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> >
> > You'll want to have:
> >
> > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > -I/p/home/jraby/PNG/libpng-1.2.34/include/
> > -I/p/home/jraby/zlib/zlib- 1.2.8/include/
> >
> > Please note that the -I and paths that follow are separated by
spaces.
> > If you keep what you have currently, I believe that it will only
> > include the last one (zlib).
> >
> > I see now that for the GRIB2C library, the setting of CFLAGS is
done
> > inside the makefile. That should work for compiling GRIB2C,
> > however, for MET you'll need to set the environment variable
> > "CFLAGS" to include "
> > -D__64BIT__" using export.
> >
> > Your change:
> >
> > #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library in
> > the original makefile.
> > # The following line names the library to the same name as that
> > expected by MET per the guidance from the MET User's Guide and the
> > MET tutorial.
> > LIB=libgrib2c.a
> >
> > looks correct to me.
> >
> > Give that a try. Hopefully, everything will go smoothly. Please
> > let us know if you encounter any other troubles.
> >
> > Thanks!
> >
> > Julie
> >
> > On Mon, Jan 9, 2017 at 9:42 AM, Raby, John W USA CIV via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <Caution-Caution-Caution-url:
> > > Caution-Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.
> > > html?id=79
> > > 100 >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > > Julie -
> > >
> > > I edited the makefile (attached as a wordpad file) as follows to
> > > accomplish the changes we discussed last week:
> > >
> > > #INC=-I/nwprod/lib/include/-->in original makefile.
> > >
> > > # The following INC settings were added by John Raby per the
> > > guidance provided by Julie Prestopnik from the MET Help Desk:
> > > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > > INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> > > INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> > > #
> > > # This "C" source code contains many uses of the C++
> > > # comment style "//". Please make sure you include the
> > > # appropriate compiler flag to allow the use of "//" comment
> > indicators.
> > > #
> > >
> > > # The following line sets the option for 64-bit.
> > > CFLAGS= -O3 -g -m64 $(INC) $(DEFS) -D__64BIT__
> > >
> > > CC=gcc
> > >
> > > #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library
in
> > > the original makefile.
> > > # The following line names the library to the same name as that
> > > expected by MET per the guidance from the MET User's Guide and
the
> > > MET tutorial.
> > > LIB=libgrib2c.a
> > >
> > > ************************************************************
> > > **********************************************************
> > >
> > > Some comments about the edit changes:
> > >
> > > I commented out the original INC statement and added 3 INC
> > > statements to account for jasper, zlib and PNG. I assume that
> > > multiple INC statements to do this will work, but I've never
done
> > > this before. Not sure if you can re-use INC for different paths
or
> > > whether you have to use INC1, INC2, ....INCX??
> > >
> > > It looked like the option for 64-bit is specified in the
makefile
> > > rather than using "export". Will this work?
> > >
> > > I commented out the original statement " LIB=libg2c_v1.6.0.a"
and
> > > added a new one to name the library as expected by MET.
> > >
> > > Could you review my changes to see if they are correct?
> > >
> > > Thanks.
> > >
> > > R/
> > > John
> > >
> > >
> > > -----Original Message-----
> > > From: Julie Prestopnik via RT
> > > [Caution-Caution-Caution-mailto:met_help at ucar.edu]
> > > Sent: Friday, January 06, 2017 2:21 PM
> > > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > > <john.w.raby2.civ at mail.mil>
> > > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
> > > about compiling GRIB2 C-Library (UNCLASSIFIED)
> > >
> > > All active links contained in this email were disabled. Please
> > > verify the identity of the sender, and confirm the authenticity
of
> > > all links contained within the message prior to copying and
> > > pasting the address to a Web browser.
> > >
> > >
> > >
> > >
> > > ----
> > >
> > > Hi John.
> > >
> > > Support for GRIB2 is disabled by default in MET. However, since
> > > you would like support for GRIB2 files you will need to compile
> > > the GRIB2C Library and enable GRIB2 support when configuring MET
with"
> > > *--enable-grib2*".
> > >
> > > I believe you would want to use the 64 bit flag if you were
> > > running on a 64 bit machine. You would do that by setting
> > > *CFLAGS="-D__64BIT__"*, either with setenv or with export (for
bash).
> > > You just need to make sure that if you configure the GRIB2C
> > > library in this way, you also configure MET in this way.
> > > Compiling MET and the GRIB2C library inconsistently may result
in
> > > a segmentation fault when reading GRIB2 files.
> > >
> > > To compile the GRIB2C library, please do the following:
> > >
> > > # Get the GRIB2C library
> > > wget
> > > Caution-Caution-Caution-Caution-
http://www.nco.ncep.noaa.gov/pmb/c
> > > odes/GRIB2
> > > /
> > > g2clib-1.6.0.tar
> > >
> > > # Untar it
> > > tar -xvf g2clib-1.6.0.tar
> > > cd g2clib-1.6.0
> > >
> > > # Open up and edit the "makefile"
> > > # Set INC =-I/path/for/include/files
> > > # Please make sure to include all idirectories where include
files
> > > # can be found (jasper/*.h and png.h pngconf.h zconf.h
zlib.h)
> > >
> > > # Compile it
> > > make
> > >
> > > I hope that helps!
> > >
> > > Julie
> > >
> > >
> > > On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> > > > Transaction: Ticket created by john.w.raby2.civ at mail.mil
> > > > Queue: met_help
> > > > Subject: question about compiling GRIB2 C-Library
(UNCLASSIFIED)
> > > > Owner: Nobody
> > > > Requestors: john.w.raby2.civ at mail.mil
> > > > Status: new
> > > > Ticket <Caution-Caution-Caution-Caution-url:
> > > > Caution-Caution-Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.
> > > > html?id=79
> > > > 100 >
> > > >
> > > >
> > > > CLASSIFICATION: UNCLASSIFIED
> > > >
> > > > Unlike zlib, png and jasper which involved the running of
> > > > ./configure before running make, unpacking of g2clib failed to
> > > > produce a configure script. The README which was produced
> > > > doesn't seem to provide much info about running ./configure.
Is
> > > > this a problem? The MET tutorial and User's Guide describe
some
> > > > specific requirement for compiling with or without the option
> > > > -D__64BIT, but it is not clear how this option is specified.
> > > > Could you clarify on this issue? Also, what are the
> > > > considerations which would help the user choose between a
> > > > configuration with the D__64BIT option vs a configuration
without it.
> > > > I am progressing with installing MET V5.2 and would like GRIB2
> > > > support.
> > > >
> > > > Thanks.
> > > >
> > > > R/
> > > > John
> > > >
> > > > Mr John W. Raby, Meteorologist
> > > > U.S. Army Research Laboratory
> > > > White Sands Missile Range, NM 88002
> > > > (575) 678-2004 DSN 258-2004
> > > > FAX (575) 678-1230 DSN 258-1230
> > > > Email: john.w.raby2.civ at mail.mil
> > > >
> > > >
> > > >
> > > > CLASSIFICATION: UNCLASSIFIED
> > > >
> > > >
> > >
> > >
> > > --
> > > Julie Prestopnik
> > > National Center for Atmospheric Research Research Applications
> > > Laboratory
> > > Phone: 303.497.8399
> > > Email: jpresto at ucar.edu
> > >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > >
> >
> >
> > --
> > Julie Prestopnik
> > National Center for Atmospheric Research Research Applications
> > Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> >
>
>
> --
> Julie Prestopnik
> National Center for Atmospheric Research Research Applications
> Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research Research Applications
Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
CLASSIFICATION: UNCLASSIFIED
------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Julie Prestopnik
Time: Wed Jan 11 13:35:53 2017
Hi John.
When I do an "ls *.h" in my g2clib-1.6.0, I see the following header
files:
drstemplates.h grib2.h gridtemplates.h pdstemplates.h
Does your directory contain those header files?
Hopefully, it does, and if I have your path correct you would set both
MET_GRIB2CINC and MET_GRIB2CLIB to /p/home/jraby/grib2c/g2clib-1.6.0.
I hope that helps.
Thanks,
Julie
On Wed, Jan 11, 2017 at 1:23 PM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
> CLASSIFICATION: UNCLASSIFIED
>
> Julie -
>
> I read the tutorial page at
> http://www.dtcenter.org/met/users/support/online_tutorial/
> METv5.2/tutorial.php?name=compilation&category=req_libs
>
> The section on GRIB2C mentions that the required library, called
> libgrib2c.a,
> is what MET will look for and that. I checked the contents of my dir
> g2clib-1.6.0 and it contains libgrib2c.a. So when I compile MET for
GRIB2
> support, I should use the two environment variables and point them
to the
> dir
> which contains libgrib2c.a.
>
> What's confusing for me is that at the page your provided the link
for,
> they
> state that you should point to the dir containing the "include" and
> "library"
> files, but in the page above they explicitly mention the dir which
contains
> libgrib2c.a. Maybe they are saying the same thing?
>
> What's your take?
>
> R/
> John
>
>
>
> -----Original Message-----
> From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, January 11, 2017 10:19 AM
> To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about
> compiling GRIB2 C-Library (UNCLASSIFIED)
>
> All active links contained in this email were disabled. Please
verify the
> identity of the sender, and confirm the authenticity of all links
contained
> within the message prior to copying and pasting the address to a Web
> browser.
>
>
>
>
> ----
>
> Hi John. There is no need to run "make install" (and in fact we
can't
> because
> there is "No rule to make target 'install'." for this library).
> When you get to:
>
> Caution-http://www.dtcenter.org/met/users/support/online_
> tutorial/METv5.2/tutorial.php?name=compilation&category=configure
>
> you'll see that it says:
>
> "If compiling support for *GRIB2*, set *$MET_GRIB2CINC* and
> *$MET_GRIB2CLIB*
> to point to the main GRIB2C directory which contains both the
include and
> library files. These are used instead of *$MET_GRIB2C* since the
main
> GRIB2C
> directory does not contain include and lib subdirectories."
>
> So you can just set these environment variables to point to the main
GRIB2C
> directory and MET should compile well.
>
> Julie
>
> On Tue, Jan 10, 2017 at 3:52 PM, Raby, John W USA CIV via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <Caution-url:
> > Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> > Julie -
> >
> > Regards the compiling of the GRIB2C library, I sent an email
earlier
> > today which mentioned that after I edited the makefile to change
"gcc" to
> > "icc"
> > per
> > your suggestion, I was able to run "make" and no messages about
> > "linking not done" appeared.
> >
> > I went ahead and ran "make install" in the following location
> > (${INSTALL_DIR))
> > or /p/home/jraby/grib2c/g2clib-1.6.0, but it was stopped with the
> > following
> > error:
> >
> > > make install
> > make: *** No rule to make target `install'. Stop.
> > excalibur:~jraby/grib2c/g2clib-1.6.0
> >
> > I'm not sure what the problem is.
> >
> > R/
> > John
> >
> >
> > -----Original Message-----
> > From: Julie Prestopnik via RT [Caution-mailto:met_help at ucar.edu]
> > Sent: Tuesday, January 10, 2017 9:23 AM
> > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > <john.w.raby2.civ at mail.mil>
> > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100]
question
> > about compiling GRIB2 C-Library (UNCLASSIFIED)
> >
> > All active links contained in this email were disabled. Please
verify
> > the identity of the sender, and confirm the authenticity of all
links
> > contained within the message prior to copying and pasting the
address
> > to a Web browser.
> >
> >
> >
> >
> > ----
> >
> > Hi John.
> >
> > I see you have a question about the message " linker input file
unused
> > because linking not done". I think that may indicate a problem
which
> > would need to be fixed before the install.
> >
> > The statement "CC=gcc" does this refer to the value of the common
> > environment variable $CC which you said for your system is "icc".
> > Please change that value in the makefile for the GRIB2C library.
The
> > same family of compilers should be used to build all of the
external
> > libraries and MET. Mixing GNU compilers with Intel compilers is
not a
> > good idea.
> >
> > Please change that "gcc" value to "icc" in the makefile and try it
again.
> > Please let me know if that makes those messages go away.
> >
> > Regarding your question about copying over the header files for
the
> > HDF-EOS libraries, I believe you want to copy them over the
include
> > directory in your *${INSTALL_DIR}*. Please give that a try and
let us
> > know if you experience any problems. In the meantime, I'll work
on
> > clarifying why it currently says "cp include/*.h ../../include/".
> >
> > Thanks,
> > Julie
> >
> > On Mon, Jan 9, 2017 at 2:49 PM, Raby, John W USA CIV via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <Caution-Caution-url:
> > > Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79
> > > 100 >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > > Julie -
> > >
> > > I edited the makefile to incorporate the changes. Then on
running
> > > make I noticed a potential issue which appeared in the screen
> > > dialog. The following statement appeared numerous times:
> > >
> > > gcc: /p/home/jraby/PNG/libpng-1.2.34/include: linker input file
> > > unused because linking not done
> > > gcc: /p/home/jraby/zlib/zlib-1.2.8/include: linker input file
unused
> > > because linking not done ar -ruv libgrib2c.a seekgb.o a -
seekgb.o
> > > rm -f seekgb.o
> > > excalibur:~jraby/grib2c/g2clib-1.6.0
> > >
> > > Does this indicate a problem which needs to be fixed before the
> install?
> > >
> > > I have one question which occurred to me as I was editing the
> > > makefile. I noticed that there is s statement "CC=gcc". Does
this
> > > refer to the value of the common environment variable $CC which
for
> > > my system (Excalibur) is "icc"
> > > not "gcc". Maybe this is no issue at all, but I wanted to ask
you
> > > about it in case it is.
> > >
> > > I also have a question about compiling the HDF-EOS library.
> > > Following the MET tutorial, I performed all the steps except the
> > > last one (cp include/*.h ../../include/.). At the point where I
am
> > > supposed to execute this statement, I am sitting in the
following
> > > directory:
> > >
> > > /p/home/jraby/hdfeos/hdfeos
> > >
> > > If I execute the cp statement as is, it looks for the target dir
up
> > > in my home
> > > (jraby) and there is no "include" dir in jraby. I need more info
as
> > > to what the intended destination is or where the target dir is
> > > supposed to be located so I can modify the path I use
accordingly.
> > >
> > > Thanks.
> > >
> > > R/
> > > John
> > >
> > > -----Original Message-----
> > > From: Julie Prestopnik via RT
> > > [Caution-Caution-mailto:met_help at ucar.edu]
> > > Sent: Monday, January 09, 2017 10:49 AM
> > > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > > <john.w.raby2.civ at mail.mil>
> > > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100]
question
> > > about compiling GRIB2 C-Library (UNCLASSIFIED)
> > >
> > > All active links contained in this email were disabled. Please
> > > verify the identity of the sender, and confirm the authenticity
of
> > > all links contained within the message prior to copying and
pasting
> > > the address to a Web browser.
> > >
> > >
> > >
> > >
> > > ----
> > >
> > > Hi John.
> > >
> > > I see that you have some questions regarding compiling the
GRIB2C
> > library.
> > > Instead of the following:
> > >
> > > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > > INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> > > INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> > >
> > > You'll want to have:
> > >
> > > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > > -I/p/home/jraby/PNG/libpng-1.2.34/include/
> > > -I/p/home/jraby/zlib/zlib- 1.2.8/include/
> > >
> > > Please note that the -I and paths that follow are separated by
spaces.
> > > If you keep what you have currently, I believe that it will only
> > > include the last one (zlib).
> > >
> > > I see now that for the GRIB2C library, the setting of CFLAGS is
done
> > > inside the makefile. That should work for compiling GRIB2C,
> > > however, for MET you'll need to set the environment variable
> > > "CFLAGS" to include "
> > > -D__64BIT__" using export.
> > >
> > > Your change:
> > >
> > > #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library
in
> > > the original makefile.
> > > # The following line names the library to the same name as that
> > > expected by MET per the guidance from the MET User's Guide and
the
> > > MET tutorial.
> > > LIB=libgrib2c.a
> > >
> > > looks correct to me.
> > >
> > > Give that a try. Hopefully, everything will go smoothly.
Please
> > > let us know if you encounter any other troubles.
> > >
> > > Thanks!
> > >
> > > Julie
> > >
> > > On Mon, Jan 9, 2017 at 9:42 AM, Raby, John W USA CIV via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <Caution-Caution-Caution-url:
> > > > Caution-Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.
> > > > html?id=79
> > > > 100 >
> > > >
> > > > CLASSIFICATION: UNCLASSIFIED
> > > >
> > > > Julie -
> > > >
> > > > I edited the makefile (attached as a wordpad file) as follows
to
> > > > accomplish the changes we discussed last week:
> > > >
> > > > #INC=-I/nwprod/lib/include/-->in original makefile.
> > > >
> > > > # The following INC settings were added by John Raby per the
> > > > guidance provided by Julie Prestopnik from the MET Help Desk:
> > > > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > > > INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> > > > INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> > > > #
> > > > # This "C" source code contains many uses of the C++
> > > > # comment style "//". Please make sure you include the
> > > > # appropriate compiler flag to allow the use of "//" comment
> > > indicators.
> > > > #
> > > >
> > > > # The following line sets the option for 64-bit.
> > > > CFLAGS= -O3 -g -m64 $(INC) $(DEFS) -D__64BIT__
> > > >
> > > > CC=gcc
> > > >
> > > > #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C
library in
> > > > the original makefile.
> > > > # The following line names the library to the same name as
that
> > > > expected by MET per the guidance from the MET User's Guide and
the
> > > > MET tutorial.
> > > > LIB=libgrib2c.a
> > > >
> > > > ************************************************************
> > > > **********************************************************
> > > >
> > > > Some comments about the edit changes:
> > > >
> > > > I commented out the original INC statement and added 3 INC
> > > > statements to account for jasper, zlib and PNG. I assume that
> > > > multiple INC statements to do this will work, but I've never
done
> > > > this before. Not sure if you can re-use INC for different
paths or
> > > > whether you have to use INC1, INC2, ....INCX??
> > > >
> > > > It looked like the option for 64-bit is specified in the
makefile
> > > > rather than using "export". Will this work?
> > > >
> > > > I commented out the original statement " LIB=libg2c_v1.6.0.a"
and
> > > > added a new one to name the library as expected by MET.
> > > >
> > > > Could you review my changes to see if they are correct?
> > > >
> > > > Thanks.
> > > >
> > > > R/
> > > > John
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Julie Prestopnik via RT
> > > > [Caution-Caution-Caution-mailto:met_help at ucar.edu]
> > > > Sent: Friday, January 06, 2017 2:21 PM
> > > > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > > > <john.w.raby2.civ at mail.mil>
> > > > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100]
question
> > > > about compiling GRIB2 C-Library (UNCLASSIFIED)
> > > >
> > > > All active links contained in this email were disabled.
Please
> > > > verify the identity of the sender, and confirm the
authenticity of
> > > > all links contained within the message prior to copying and
> > > > pasting the address to a Web browser.
> > > >
> > > >
> > > >
> > > >
> > > > ----
> > > >
> > > > Hi John.
> > > >
> > > > Support for GRIB2 is disabled by default in MET. However,
since
> > > > you would like support for GRIB2 files you will need to
compile
> > > > the GRIB2C Library and enable GRIB2 support when configuring
MET
> with"
> > > > *--enable-grib2*".
> > > >
> > > > I believe you would want to use the 64 bit flag if you were
> > > > running on a 64 bit machine. You would do that by setting
> > > > *CFLAGS="-D__64BIT__"*, either with setenv or with export (for
bash).
> > > > You just need to make sure that if you configure the GRIB2C
> > > > library in this way, you also configure MET in this way.
> > > > Compiling MET and the GRIB2C library inconsistently may result
in
> > > > a segmentation fault when reading GRIB2 files.
> > > >
> > > > To compile the GRIB2C library, please do the following:
> > > >
> > > > # Get the GRIB2C library
> > > > wget
> > > > Caution-Caution-Caution-Caution-
http://www.nco.ncep.noaa.gov/pmb/c
> > > > odes/GRIB2
> > > > /
> > > > g2clib-1.6.0.tar
> > > >
> > > > # Untar it
> > > > tar -xvf g2clib-1.6.0.tar
> > > > cd g2clib-1.6.0
> > > >
> > > > # Open up and edit the "makefile"
> > > > # Set INC =-I/path/for/include/files
> > > > # Please make sure to include all idirectories where
include files
> > > > # can be found (jasper/*.h and png.h pngconf.h zconf.h
zlib.h)
> > > >
> > > > # Compile it
> > > > make
> > > >
> > > > I hope that helps!
> > > >
> > > > Julie
> > > >
> > > >
> > > > On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> > > > > Transaction: Ticket created by john.w.raby2.civ at mail.mil
> > > > > Queue: met_help
> > > > > Subject: question about compiling GRIB2 C-Library
> (UNCLASSIFIED)
> > > > > Owner: Nobody
> > > > > Requestors: john.w.raby2.civ at mail.mil
> > > > > Status: new
> > > > > Ticket <Caution-Caution-Caution-Caution-url:
> > > > > Caution-Caution-Caution-Caution-https://rt.rap.ucar.
> edu/rt/Ticket/Display.
> > > > > html?id=79
> > > > > 100 >
> > > > >
> > > > >
> > > > > CLASSIFICATION: UNCLASSIFIED
> > > > >
> > > > > Unlike zlib, png and jasper which involved the running of
> > > > > ./configure before running make, unpacking of g2clib failed
to
> > > > > produce a configure script. The README which was produced
> > > > > doesn't seem to provide much info about running ./configure.
Is
> > > > > this a problem? The MET tutorial and User's Guide describe
some
> > > > > specific requirement for compiling with or without the
option
> > > > > -D__64BIT, but it is not clear how this option is specified.
> > > > > Could you clarify on this issue? Also, what are the
> > > > > considerations which would help the user choose between a
> > > > > configuration with the D__64BIT option vs a configuration
without
> it.
> > > > > I am progressing with installing MET V5.2 and would like
GRIB2
> > > > > support.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > R/
> > > > > John
> > > > >
> > > > > Mr John W. Raby, Meteorologist
> > > > > U.S. Army Research Laboratory
> > > > > White Sands Missile Range, NM 88002
> > > > > (575) 678-2004 DSN 258-2004
> > > > > FAX (575) 678-1230 DSN 258-1230
> > > > > Email: john.w.raby2.civ at mail.mil
> > > > >
> > > > >
> > > > >
> > > > > CLASSIFICATION: UNCLASSIFIED
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Julie Prestopnik
> > > > National Center for Atmospheric Research Research Applications
> > > > Laboratory
> > > > Phone: 303.497.8399
> > > > Email: jpresto at ucar.edu
> > > >
> > > >
> > > > CLASSIFICATION: UNCLASSIFIED
> > > >
> > > >
> > >
> > >
> > > --
> > > Julie Prestopnik
> > > National Center for Atmospheric Research Research Applications
> > > Laboratory
> > > Phone: 303.497.8399
> > > Email: jpresto at ucar.edu
> > >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > >
> >
> >
> > --
> > Julie Prestopnik
> > National Center for Atmospheric Research Research Applications
> > Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> >
>
>
> --
> Julie Prestopnik
> National Center for Atmospheric Research Research Applications
Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
------------------------------------------------
Subject: question about compiling GRIB2 C-Library (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Wed Jan 11 14:19:59 2017
CLASSIFICATION: UNCLASSIFIED
Julie -
In answer to your question, see the following:
excalibur:~jraby/grib2c/g2clib-1.6.0
> ls *.h
drstemplates.h* grib2.h* gridtemplates.h* pdstemplates.h*
It looks as if I have the right header files. This has definitely been
helpful.
I'll consider the GRIB2 C-Library installed at this point. Will carry
this
over when I reach the step involving the GRIB2 C-Library in compiling
MET as
you've pointed out.
Thanks.
R/
John
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, January 11, 2017 1:36 PM
To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
about
compiling GRIB2 C-Library (UNCLASSIFIED)
All active links contained in this email were disabled. Please verify
the
identity of the sender, and confirm the authenticity of all links
contained
within the message prior to copying and pasting the address to a Web
browser.
----
Hi John.
When I do an "ls *.h" in my g2clib-1.6.0, I see the following header
files:
drstemplates.h grib2.h gridtemplates.h pdstemplates.h
Does your directory contain those header files?
Hopefully, it does, and if I have your path correct you would set both
MET_GRIB2CINC and MET_GRIB2CLIB to /p/home/jraby/grib2c/g2clib-1.6.0.
I hope that helps.
Thanks,
Julie
On Wed, Jan 11, 2017 at 1:23 PM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> <Caution-url:
> Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79100 >
>
> CLASSIFICATION: UNCLASSIFIED
>
> Julie -
>
> I read the tutorial page at
> Caution-http://www.dtcenter.org/met/users/support/online_tutorial/
> METv5.2/tutorial.php?name=compilation&category=req_libs
>
> The section on GRIB2C mentions that the required library, called
> libgrib2c.a, is what MET will look for and that. I checked the
> contents of my dir
> g2clib-1.6.0 and it contains libgrib2c.a. So when I compile MET for
> GRIB2 support, I should use the two environment variables and point
> them to the dir which contains libgrib2c.a.
>
> What's confusing for me is that at the page your provided the link
> for, they state that you should point to the dir containing the
> "include" and "library"
> files, but in the page above they explicitly mention the dir which
> contains libgrib2c.a. Maybe they are saying the same thing?
>
> What's your take?
>
> R/
> John
>
>
>
> -----Original Message-----
> From: Julie Prestopnik via RT [Caution-mailto:met_help at ucar.edu]
> Sent: Wednesday, January 11, 2017 10:19 AM
> To: Raby, John W CIV USARMY RDECOM ARL (US)
> <john.w.raby2.civ at mail.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100] question
> about compiling GRIB2 C-Library (UNCLASSIFIED)
>
> All active links contained in this email were disabled. Please
verify
> the identity of the sender, and confirm the authenticity of all
links
> contained within the message prior to copying and pasting the
address
> to a Web browser.
>
>
>
>
> ----
>
> Hi John. There is no need to run "make install" (and in fact we
can't
> because there is "No rule to make target 'install'." for this
> library).
> When you get to:
>
> Caution-Caution-http://www.dtcenter.org/met/users/support/online_
> tutorial/METv5.2/tutorial.php?name=compilation&category=configure
>
> you'll see that it says:
>
> "If compiling support for *GRIB2*, set *$MET_GRIB2CINC* and
> *$MET_GRIB2CLIB*
> to point to the main GRIB2C directory which contains both the
include
> and library files. These are used instead of *$MET_GRIB2C* since the
> main GRIB2C directory does not contain include and lib
> subdirectories."
>
> So you can just set these environment variables to point to the main
> GRIB2C directory and MET should compile well.
>
> Julie
>
> On Tue, Jan 10, 2017 at 3:52 PM, Raby, John W USA CIV via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <Caution-Caution-url:
> > Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79
> > 100 >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> > Julie -
> >
> > Regards the compiling of the GRIB2C library, I sent an email
earlier
> > today which mentioned that after I edited the makefile to change
> > "gcc" to "icc"
> > per
> > your suggestion, I was able to run "make" and no messages about
> > "linking not done" appeared.
> >
> > I went ahead and ran "make install" in the following location
> > (${INSTALL_DIR))
> > or /p/home/jraby/grib2c/g2clib-1.6.0, but it was stopped with the
> > following
> > error:
> >
> > > make install
> > make: *** No rule to make target `install'. Stop.
> > excalibur:~jraby/grib2c/g2clib-1.6.0
> >
> > I'm not sure what the problem is.
> >
> > R/
> > John
> >
> >
> > -----Original Message-----
> > From: Julie Prestopnik via RT
> > [Caution-Caution-mailto:met_help at ucar.edu]
> > Sent: Tuesday, January 10, 2017 9:23 AM
> > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > <john.w.raby2.civ at mail.mil>
> > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100]
question
> > about compiling GRIB2 C-Library (UNCLASSIFIED)
> >
> > All active links contained in this email were disabled. Please
> > verify the identity of the sender, and confirm the authenticity of
> > all links contained within the message prior to copying and
pasting
> > the address to a Web browser.
> >
> >
> >
> >
> > ----
> >
> > Hi John.
> >
> > I see you have a question about the message " linker input file
> > unused because linking not done". I think that may indicate a
> > problem which would need to be fixed before the install.
> >
> > The statement "CC=gcc" does this refer to the value of the common
> > environment variable $CC which you said for your system is "icc".
> > Please change that value in the makefile for the GRIB2C library.
> > The same family of compilers should be used to build all of the
> > external libraries and MET. Mixing GNU compilers with Intel
> > compilers is not a good idea.
> >
> > Please change that "gcc" value to "icc" in the makefile and try it
again.
> > Please let me know if that makes those messages go away.
> >
> > Regarding your question about copying over the header files for
the
> > HDF-EOS libraries, I believe you want to copy them over the
include
> > directory in your *${INSTALL_DIR}*. Please give that a try and
let
> > us know if you experience any problems. In the meantime, I'll
work
> > on clarifying why it currently says "cp include/*.h
../../include/".
> >
> > Thanks,
> > Julie
> >
> > On Mon, Jan 9, 2017 at 2:49 PM, Raby, John W USA CIV via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <Caution-Caution-Caution-url:
> > > Caution-Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.
> > > html?id=79
> > > 100 >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > > Julie -
> > >
> > > I edited the makefile to incorporate the changes. Then on
running
> > > make I noticed a potential issue which appeared in the screen
> > > dialog. The following statement appeared numerous times:
> > >
> > > gcc: /p/home/jraby/PNG/libpng-1.2.34/include: linker input file
> > > unused because linking not done
> > > gcc: /p/home/jraby/zlib/zlib-1.2.8/include: linker input file
> > > unused because linking not done ar -ruv libgrib2c.a seekgb.o a
-
> > > seekgb.o rm -f seekgb.o
> > > excalibur:~jraby/grib2c/g2clib-1.6.0
> > >
> > > Does this indicate a problem which needs to be fixed before the
> install?
> > >
> > > I have one question which occurred to me as I was editing the
> > > makefile. I noticed that there is s statement "CC=gcc". Does
this
> > > refer to the value of the common environment variable $CC which
> > > for my system (Excalibur) is "icc"
> > > not "gcc". Maybe this is no issue at all, but I wanted to ask
you
> > > about it in case it is.
> > >
> > > I also have a question about compiling the HDF-EOS library.
> > > Following the MET tutorial, I performed all the steps except the
> > > last one (cp include/*.h ../../include/.). At the point where I
am
> > > supposed to execute this statement, I am sitting in the
following
> > > directory:
> > >
> > > /p/home/jraby/hdfeos/hdfeos
> > >
> > > If I execute the cp statement as is, it looks for the target dir
> > > up in my home
> > > (jraby) and there is no "include" dir in jraby. I need more info
> > > as to what the intended destination is or where the target dir
is
> > > supposed to be located so I can modify the path I use
accordingly.
> > >
> > > Thanks.
> > >
> > > R/
> > > John
> > >
> > > -----Original Message-----
> > > From: Julie Prestopnik via RT
> > > [Caution-Caution-Caution-mailto:met_help at ucar.edu]
> > > Sent: Monday, January 09, 2017 10:49 AM
> > > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > > <john.w.raby2.civ at mail.mil>
> > > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100]
> > > question about compiling GRIB2 C-Library (UNCLASSIFIED)
> > >
> > > All active links contained in this email were disabled. Please
> > > verify the identity of the sender, and confirm the authenticity
of
> > > all links contained within the message prior to copying and
> > > pasting the address to a Web browser.
> > >
> > >
> > >
> > >
> > > ----
> > >
> > > Hi John.
> > >
> > > I see that you have some questions regarding compiling the
GRIB2C
> > library.
> > > Instead of the following:
> > >
> > > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > > INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> > > INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> > >
> > > You'll want to have:
> > >
> > > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > > -I/p/home/jraby/PNG/libpng-1.2.34/include/
> > > -I/p/home/jraby/zlib/zlib- 1.2.8/include/
> > >
> > > Please note that the -I and paths that follow are separated by
spaces.
> > > If you keep what you have currently, I believe that it will only
> > > include the last one (zlib).
> > >
> > > I see now that for the GRIB2C library, the setting of CFLAGS is
> > > done inside the makefile. That should work for compiling
GRIB2C,
> > > however, for MET you'll need to set the environment variable
> > > "CFLAGS" to include "
> > > -D__64BIT__" using export.
> > >
> > > Your change:
> > >
> > > #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C library
in
> > > the original makefile.
> > > # The following line names the library to the same name as that
> > > expected by MET per the guidance from the MET User's Guide and
the
> > > MET tutorial.
> > > LIB=libgrib2c.a
> > >
> > > looks correct to me.
> > >
> > > Give that a try. Hopefully, everything will go smoothly.
Please
> > > let us know if you encounter any other troubles.
> > >
> > > Thanks!
> > >
> > > Julie
> > >
> > > On Mon, Jan 9, 2017 at 9:42 AM, Raby, John W USA CIV via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <Caution-Caution-Caution-Caution-url:
> > > > Caution-Caution-Caution-Caution-
https://rt.rap.ucar.edu/rt/Ticket/Display.
> > > > html?id=79
> > > > 100 >
> > > >
> > > > CLASSIFICATION: UNCLASSIFIED
> > > >
> > > > Julie -
> > > >
> > > > I edited the makefile (attached as a wordpad file) as follows
to
> > > > accomplish the changes we discussed last week:
> > > >
> > > > #INC=-I/nwprod/lib/include/-->in original makefile.
> > > >
> > > > # The following INC settings were added by John Raby per the
> > > > guidance provided by Julie Prestopnik from the MET Help Desk:
> > > > INC=-I/p/home/jraby/jasper/jasper-1.900.2/include/jasper/
> > > > INC=-I/p/home/jraby/PNG/libpng-1.2.34/include/
> > > > INC=-I/p/home/jraby/zlib/zlib-1.2.8/include/
> > > > #
> > > > # This "C" source code contains many uses of the C++
> > > > # comment style "//". Please make sure you include the
> > > > # appropriate compiler flag to allow the use of "//" comment
> > > indicators.
> > > > #
> > > >
> > > > # The following line sets the option for 64-bit.
> > > > CFLAGS= -O3 -g -m64 $(INC) $(DEFS) -D__64BIT__
> > > >
> > > > CC=gcc
> > > >
> > > > #LIB=libg2c_v1.6.0.a--> This was the name of the GRIB2C
library
> > > > in the original makefile.
> > > > # The following line names the library to the same name as
that
> > > > expected by MET per the guidance from the MET User's Guide and
> > > > the MET tutorial.
> > > > LIB=libgrib2c.a
> > > >
> > > > ************************************************************
> > > > **********************************************************
> > > >
> > > > Some comments about the edit changes:
> > > >
> > > > I commented out the original INC statement and added 3 INC
> > > > statements to account for jasper, zlib and PNG. I assume that
> > > > multiple INC statements to do this will work, but I've never
> > > > done this before. Not sure if you can re-use INC for different
> > > > paths or whether you have to use INC1, INC2, ....INCX??
> > > >
> > > > It looked like the option for 64-bit is specified in the
> > > > makefile rather than using "export". Will this work?
> > > >
> > > > I commented out the original statement " LIB=libg2c_v1.6.0.a"
> > > > and added a new one to name the library as expected by MET.
> > > >
> > > > Could you review my changes to see if they are correct?
> > > >
> > > > Thanks.
> > > >
> > > > R/
> > > > John
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Julie Prestopnik via RT
> > > > [Caution-Caution-Caution-Caution-mailto:met_help at ucar.edu]
> > > > Sent: Friday, January 06, 2017 2:21 PM
> > > > To: Raby, John W CIV USARMY RDECOM ARL (US)
> > > > <john.w.raby2.civ at mail.mil>
> > > > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #79100]
question
> > > > about compiling GRIB2 C-Library (UNCLASSIFIED)
> > > >
> > > > All active links contained in this email were disabled.
Please
> > > > verify the identity of the sender, and confirm the
authenticity
> > > > of all links contained within the message prior to copying and
> > > > pasting the address to a Web browser.
> > > >
> > > >
> > > >
> > > >
> > > > ----
> > > >
> > > > Hi John.
> > > >
> > > > Support for GRIB2 is disabled by default in MET. However,
since
> > > > you would like support for GRIB2 files you will need to
compile
> > > > the GRIB2C Library and enable GRIB2 support when configuring
MET
> with"
> > > > *--enable-grib2*".
> > > >
> > > > I believe you would want to use the 64 bit flag if you were
> > > > running on a 64 bit machine. You would do that by setting
> > > > *CFLAGS="-D__64BIT__"*, either with setenv or with export (for
bash).
> > > > You just need to make sure that if you configure the GRIB2C
> > > > library in this way, you also configure MET in this way.
> > > > Compiling MET and the GRIB2C library inconsistently may result
> > > > in a segmentation fault when reading GRIB2 files.
> > > >
> > > > To compile the GRIB2C library, please do the following:
> > > >
> > > > # Get the GRIB2C library
> > > > wget
> > > > Caution-Caution-Caution-Caution-Caution-
http://www.nco.ncep.noaa
> > > > .gov/pmb/c
> > > > odes/GRIB2
> > > > /
> > > > g2clib-1.6.0.tar
> > > >
> > > > # Untar it
> > > > tar -xvf g2clib-1.6.0.tar
> > > > cd g2clib-1.6.0
> > > >
> > > > # Open up and edit the "makefile"
> > > > # Set INC =-I/path/for/include/files
> > > > # Please make sure to include all idirectories where
include files
> > > > # can be found (jasper/*.h and png.h pngconf.h zconf.h
zlib.h)
> > > >
> > > > # Compile it
> > > > make
> > > >
> > > > I hope that helps!
> > > >
> > > > Julie
> > > >
> > > >
> > > > On Fri, Jan 6, 2017 at 1:11 PM, Raby, John W USA CIV via RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > Fri Jan 06 13:11:44 2017: Request 79100 was acted upon.
> > > > > Transaction: Ticket created by john.w.raby2.civ at mail.mil
> > > > > Queue: met_help
> > > > > Subject: question about compiling GRIB2 C-Library
> (UNCLASSIFIED)
> > > > > Owner: Nobody
> > > > > Requestors: john.w.raby2.civ at mail.mil
> > > > > Status: new
> > > > > Ticket <Caution-Caution-Caution-Caution-Caution-url:
> > > > > Caution-Caution-Caution-Caution-Caution-https://rt.rap.ucar.
> edu/rt/Ticket/Display.
> > > > > html?id=79
> > > > > 100 >
> > > > >
> > > > >
> > > > > CLASSIFICATION: UNCLASSIFIED
> > > > >
> > > > > Unlike zlib, png and jasper which involved the running of
> > > > > ./configure before running make, unpacking of g2clib failed
to
> > > > > produce a configure script. The README which was produced
> > > > > doesn't seem to provide much info about running ./configure.
> > > > > Is this a problem? The MET tutorial and User's Guide
describe
> > > > > some specific requirement for compiling with or without the
> > > > > option -D__64BIT, but it is not clear how this option is
specified.
> > > > > Could you clarify on this issue? Also, what are the
> > > > > considerations which would help the user choose between a
> > > > > configuration with the D__64BIT option vs a configuration
> > > > > without
> it.
> > > > > I am progressing with installing MET V5.2 and would like
GRIB2
> > > > > support.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > R/
> > > > > John
> > > > >
> > > > > Mr John W. Raby, Meteorologist U.S. Army Research Laboratory
> > > > > White Sands Missile Range, NM 88002
> > > > > (575) 678-2004 DSN 258-2004
> > > > > FAX (575) 678-1230 DSN 258-1230
> > > > > Email: john.w.raby2.civ at mail.mil
> > > > >
> > > > >
> > > > >
> > > > > CLASSIFICATION: UNCLASSIFIED
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Julie Prestopnik
> > > > National Center for Atmospheric Research Research Applications
> > > > Laboratory
> > > > Phone: 303.497.8399
> > > > Email: jpresto at ucar.edu
> > > >
> > > >
> > > > CLASSIFICATION: UNCLASSIFIED
> > > >
> > > >
> > >
> > >
> > > --
> > > Julie Prestopnik
> > > National Center for Atmospheric Research Research Applications
> > > Laboratory
> > > Phone: 303.497.8399
> > > Email: jpresto at ucar.edu
> > >
> > >
> > > CLASSIFICATION: UNCLASSIFIED
> > >
> > >
> >
> >
> > --
> > Julie Prestopnik
> > National Center for Atmospheric Research Research Applications
> > Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> >
> > CLASSIFICATION: UNCLASSIFIED
> >
> >
>
>
> --
> Julie Prestopnik
> National Center for Atmospheric Research Research Applications
> Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
--
Julie Prestopnik
National Center for Atmospheric Research Research Applications
Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
CLASSIFICATION: UNCLASSIFIED
------------------------------------------------
More information about the Met_help
mailing list