[Met_help] [rt.rap.ucar.edu #42052] History for Upgrade to MET 3
RAL HelpDesk {for John Halley Gotway}
met_help at ucar.edu
Wed Nov 10 12:59:30 MST 2010
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
I was looking in the documentation (release notes and user guide) and it seemed to written more for an initial installation instead of an upgrade. Should I place all the files in the same directories that the version 2 is in? Do I need to redownload BUFLIB, NetCDF, GSL and recompile all? Are all my data and config files in the previous MET directory structure going to be safe (not erased)?
Thanks
Bob Craig
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #42052] Upgrade to MET 3
From: John Halley Gotway
Time: Wed Nov 10 11:11:48 2010
Bob,
Yes, there's isn't really an "upgrade" option. It is really just a
new build. I'd put the METv3.0 tar file at the same level as the
existing METv2.0 directory. When you untar/uncompress that file,
it'll create a new directory named METv3.0. Regarding BUFRLIB,
NetCDF, and GSL, you should just be able to link to the existing
versions you have rather than rebuilding them.
Please do be sure to retrieve the latest set of patches for METv3.0
from:
http://www.dtcenter.org/met/users/support/known_issues/METv3.0/index.php
When you configure the METv3.0 Makefile, just copy over the settings
you used in your METv2.0 Makefile for:
CXX, FC, NETCDF_BASE, BUFR_BASE, and GSL_BASE
And if you'd like to compile the WWMCA tools, you'll need enable their
compilation by setting:
DISABLE_TOOLS = 0
And then compile METv3.0 by typing "make" in the top-level directory.
When you run the METv3.0 tools, by default, they'll write their output
to the METv3.0/out/tool_name directory. You can always
override that using the "-outdir" command line option.
Please give that a shot and let us know if you run into any problems.
Thanks,
John
On 11/10/2010 10:21 AM, RAL HelpDesk {for Craig, Robert J Civ USAF
AFWA 16 WS/WXN} wrote:
>
> Wed Nov 10 10:21:00 2010: Request 42052 was acted upon.
> Transaction: Ticket created by craigr at offutt.af.mil
> Queue: met_help
> Subject: Upgrade to MET 3
> Owner: Nobody
> Requestors: craigr at offutt.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=42052 >
>
>
> I was looking in the documentation (release notes and user guide)
and it seemed to written more for an initial installation instead of
an upgrade. Should I place all the files in the same directories
that the version 2 is in? Do I need to redownload BUFLIB, NetCDF,
GSL and recompile all? Are all my data and config files in the
previous MET directory structure going to be safe (not erased)?
>
> Thanks
> Bob Craig
------------------------------------------------
Subject: Upgrade to MET 3
From: Craig, Robert J Civ USAF AFWA 16 WS/WXN
Time: Wed Nov 10 12:55:03 2010
John, I did what you said. When I do the make I get the following
errors:
"Makefile", line 199: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 201: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 202: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 204: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 205: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 207: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 208: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 210: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 211: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 213: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 214: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 216: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 217: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 219: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 220: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 222: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 223: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 225: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 226: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 228: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 229: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 231: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 232: make: 1254-055 Dependency line needs colon or
double
colon operator.
"Makefile", line 234: make: 1254-055 Dependency line needs colon or
double
colon operator.
make: 1254-058 Fatal errors encountered -- cannot continue.
The make file is attached. Diffing this file with the previous
indicates all
the paths have be set properly.
Any ideas.
-----Original Message-----
From: RAL HelpDesk {for John Halley Gotway} [mailto:met_help at ucar.edu]
Sent: Wednesday, November 10, 2010 12:12 PM
To: Craig, Robert J Civ USAF AFWA 16 WS/WXN
Subject: Re: [rt.rap.ucar.edu #42052] Upgrade to MET 3
Bob,
Yes, there's isn't really an "upgrade" option. It is really just a
new build.
I'd put the METv3.0 tar file at the same level as the existing METv2.0
directory. When you untar/uncompress that file,
it'll create a new directory named METv3.0. Regarding BUFRLIB,
NetCDF, and
GSL, you should just be able to link to the existing versions you have
rather
than rebuilding them.
Please do be sure to retrieve the latest set of patches for METv3.0
from:
http://www.dtcenter.org/met/users/support/known_issues/METv3.0/index.php
When you configure the METv3.0 Makefile, just copy over the settings
you used
in your METv2.0 Makefile for:
CXX, FC, NETCDF_BASE, BUFR_BASE, and GSL_BASE
And if you'd like to compile the WWMCA tools, you'll need enable their
compilation by setting:
DISABLE_TOOLS = 0
And then compile METv3.0 by typing "make" in the top-level directory.
When
you run the METv3.0 tools, by default, they'll write their output to
the
METv3.0/out/tool_name directory. You can always
override that using the "-outdir" command line option.
Please give that a shot and let us know if you run into any problems.
Thanks,
John
On 11/10/2010 10:21 AM, RAL HelpDesk {for Craig, Robert J Civ USAF
AFWA 16
WS/WXN} wrote:
>
> Wed Nov 10 10:21:00 2010: Request 42052 was acted upon.
> Transaction: Ticket created by craigr at offutt.af.mil
> Queue: met_help
> Subject: Upgrade to MET 3
> Owner: Nobody
> Requestors: craigr at offutt.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=42052 >
>
>
> I was looking in the documentation (release notes and user guide)
and it
> seemed to written more for an initial installation instead of an
upgrade.
> Should I place all the files in the same directories that the
version 2 is
> in? Do I need to redownload BUFLIB, NetCDF, GSL and recompile all?
Are
> all my data and config files in the previous MET directory structure
going
> to be safe (not erased)?
>
> Thanks
> Bob Craig
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #42052] Upgrade to MET 3
From: John Halley Gotway
Time: Wed Nov 10 12:59:24 2010
Bob,
Glad you figured it out. I'll go ahead and resolve this ticket. Feel
free to write if more issues come up.
John
On 11/10/2010 12:55 PM, RAL HelpDesk {for Craig, Robert J Civ USAF
AFWA 16 WS/WXN} wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=42052 >
>
> John, I did what you said. When I do the make I get the following
errors:
>
> "Makefile", line 199: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 201: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 202: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 204: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 205: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 207: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 208: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 210: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 211: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 213: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 214: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 216: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 217: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 219: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 220: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 222: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 223: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 225: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 226: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 228: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 229: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 231: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 232: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> "Makefile", line 234: make: 1254-055 Dependency line needs colon or
double
> colon operator.
> make: 1254-058 Fatal errors encountered -- cannot continue.
>
> The make file is attached. Diffing this file with the previous
indicates all
> the paths have be set properly.
>
> Any ideas.
>
>
>
> -----Original Message-----
> From: RAL HelpDesk {for John Halley Gotway}
[mailto:met_help at ucar.edu]
> Sent: Wednesday, November 10, 2010 12:12 PM
> To: Craig, Robert J Civ USAF AFWA 16 WS/WXN
> Subject: Re: [rt.rap.ucar.edu #42052] Upgrade to MET 3
>
> Bob,
>
> Yes, there's isn't really an "upgrade" option. It is really just a
new build.
> I'd put the METv3.0 tar file at the same level as the existing
METv2.0
> directory. When you untar/uncompress that file,
> it'll create a new directory named METv3.0. Regarding BUFRLIB,
NetCDF, and
> GSL, you should just be able to link to the existing versions you
have rather
> than rebuilding them.
>
> Please do be sure to retrieve the latest set of patches for METv3.0
from:
>
http://www.dtcenter.org/met/users/support/known_issues/METv3.0/index.php
>
> When you configure the METv3.0 Makefile, just copy over the settings
you used
> in your METv2.0 Makefile for:
> CXX, FC, NETCDF_BASE, BUFR_BASE, and GSL_BASE
>
> And if you'd like to compile the WWMCA tools, you'll need enable
their
> compilation by setting:
> DISABLE_TOOLS = 0
>
> And then compile METv3.0 by typing "make" in the top-level
directory. When
> you run the METv3.0 tools, by default, they'll write their output to
the
> METv3.0/out/tool_name directory. You can always
> override that using the "-outdir" command line option.
>
> Please give that a shot and let us know if you run into any
problems.
>
> Thanks,
> John
>
>
> On 11/10/2010 10:21 AM, RAL HelpDesk {for Craig, Robert J Civ USAF
AFWA 16
> WS/WXN} wrote:
>>
>> Wed Nov 10 10:21:00 2010: Request 42052 was acted upon.
>> Transaction: Ticket created by craigr at offutt.af.mil
>> Queue: met_help
>> Subject: Upgrade to MET 3
>> Owner: Nobody
>> Requestors: craigr at offutt.af.mil
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=42052 >
>>
>>
>> I was looking in the documentation (release notes and user guide)
and it
>> seemed to written more for an initial installation instead of an
upgrade.
>> Should I place all the files in the same directories that the
version 2 is
>> in? Do I need to redownload BUFLIB, NetCDF, GSL and recompile
all? Are
>> all my data and config files in the previous MET directory
structure going
>> to be safe (not erased)?
>>
>> Thanks
>> Bob Craig
>
>
------------------------------------------------
More information about the Met_help
mailing list