Hi Gerry,
Don't worrry about it.
For just running "ncl", it doesn't care where the files are. It uses
NCARG_ROOT
to find things like fonts, map databases, and Udunits files.
If you need to compile programs, it doesn't matter either as long
as you have -L$NCARG_ROOT/lib on your compilation line.
If you use any of the nhlcc, ncargcc, nhlf77, ncargf77 type of
helper compilation scripts, they will automatically include -L
$NCARG_ROOT/lib
on the compile line for you.
If the "lib" bothers you, you can certainly rename "lib" to "lib64",
but then
you will need to additionall set the NCARG_LIB environment variable
to this path. For example, if you installed to "/usr/local", and
moved the "/usr/local/lib" files to "/usr/local/lib64", then you
would need this:
setenv NCARG_LIB /usr/local/lib64 --> needed if "lib" changed to
"lib64"
in addition to:
setenv ROOT /usr/local
--Mary
On Apr 16, 2010, at 3:12 PM, Gerry Creager wrote:
> I just downloaded and installed the 64bit codes. When I
> untarred/gunzipped, I didn't see a lib64 entry. Did I miss
> something, or
> should I not worry about it?
>
> Thanks, Gerry
> _______________________________________________
> ncl-talk mailing list
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
_______________________________________________
ncl-talk mailing list
List instructions, subscriber options, unsubscribe:
http://mailman.ucar.edu/mailman/listinfo/ncl-talk
Received on Fri Apr 16 15:34:29 2010
This archive was generated by hypermail 2.1.8 : Fri Apr 16 2010 - 16:21:29 MDT