Re: DAP server error using octcdf-1.1.6 (octave 3.6.4)

[Marko Kvakić]

On 2 July 2013 10:30, Alexander Barth <address@hidden> wrote:
>
> Am 01.07.2013 09:08 schrieb "Marko Kvakić" <address@hidden>:
>
>
>>
>> On 30 June 2013 22:54, Alexander Barth <address@hidden> wrote:
>> > Dear Marko,
>> >
>> > Can you give a minimal example code which shows this error?
>> > The following works here:
>> >>> pkg load octcdf
>> >>> nc =
>> >>>
>> >>> netcdf('http://www.esrl.noaa.gov/psd/thredds/dodsC/Datasets/NARR/monolevel/dlwrf.2007.nc','r');
>> >>> v = nc{'dlwrf'}(1,1,1)
>> > v = -28192
>> >>> v = nc{'dlwrf'}(1,:,:);
>> >>> close(nc)
>> >
>> > Thanks
>> > Alex
>>
>> Hi Alex,
>>
>> The code i used is the same as yours.
>> Even trying to extract 1 point doesn't succeed, with the "DAP server
>> error shown"...
>>
>> I thinking i didn't compile octcdf properly after all
>>
>> I'm working on a computer without root permission, which has an older
>> version of netcdf (4.1.3).
>> Using "ncdump" from that version the same problem happens, so i think
>> octcdf got linked with it.
>>
>> Is there a way of checking which library/headers were used during the
>> compilation of octcdf?
>
> Yes, use the option -verbose.
>
> What does "which nc-config" and "nc-conflig --libs" (in shell) return? Does
> this correspond to the library that you want to use?
>
> If not, define our PATH
>
> export PATH="/path/to/the/right/bin/nc-config:$PATH"
>
> and similarily for LD_LIBRARY_PATH
>
> export LD_LIBRARY_PATH="/path/to/the/right/lib:$LD_LIBRARY_PATH"
>
> Cheers,
>
> Alex
>

Yes, it was being linked to the older library.
The variable PATH already had the sought directories in front.

But it is working now, after defining LD_LIBRARY_PATH aswell.
The toolbox now works like a charm.

Thank you for your help once more.
Kind regards,
Marko