[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20040806: netCDF under Linux (cont.)

>From: "michael bane" <address@hidden>
>Organization: UMIST
>Keywords: 200408061104.i76B4u2W029386 netCDF Linux build

Hi Michael,

>> >I'm starting with netCDF and am having trouble
>> >getting it to compile under Linux.

>Yes. Although I've discovered by LD_LIBRARY_PATH wasn't set so now I'm
>getting somewhere ;)

Under Linux, LD_LIBRARY_PATH shouldn't need to be set -- unless your
Linux installation is highly unusual.

>It all seems to build but I do get lots of failures for 'make test'. I'll
>see if I can see anything silly I've done before getting back to you.

OK.  If/when you do get back to us, please include a listing of
environment variables you have defined (output of 'env') and a
complete listing of the 'make test' output.

>However what I really wish to know (the above is just trying it out!) is,
>for Linux, is there an "optimum" hardware/operating system/compilers
>combination you recommend/support?

No, not really.  We have a large number of users of the netCDF under
Linux, and the version of Linux they are using varies widely.  We
typically never get much, if any, comment about the specific hardware
they are running on unless it is unusual (e.g., CRAY, Linux on SGI, etc.)

>In particular, this is with getting
>netCDF working with models-3 on a new machine I have a grant for. (I guess I
>should ask the models-3 people about the parallel efficiency of their code
>but we're probably talking just a uni- or dual- processor box at the
>moment.)

I am sorry to say that I know nothing about models-3.

re: you are not subscribed only to the netcdfgroup list

>That will do fine for now.
>Thanks once again, Michael

No worries.

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.

>From address@hidden  Fri Aug  6 13:51:50 2004

At 09:38 06/08/2004 -0600, you wrote:
> >Yes. Although I've discovered by LD_LIBRARY_PATH wasn't set so now I'm
> >getting somewhere ;)
>
>Under Linux, LD_LIBRARY_PATH shouldn't need to be set -- unless your
>Linux installation is highly unusual.

This was needed for icc (v8 on RedHat 9) to find library (not at work so 
not got exact name but something like libcptrs.c) when it was checking C++ 
compilation [without LD_LIB_PATH or -static it failed due to conftest.C 
giving run time error]

More on the rest when I'm next in work

Cheers! Michael