Build NCO/OpenDAP enabled for Fedora7
Command-line operators for netCDF and HDF files
Brought to you by:
zender
Menu
▾
▴
Hi,
I successfully experimented to build NCO as OpenDAP client for Fedora7 and I just would like to give my feelings.
1) Actually, NCO 3.9.2 was successfully built using libnc-dap-3-7-0 and libdap-3-7-8 sources and g++ compiler (it did'not worked with older libdap versions).
2) Be aware not to install libnc-dap-3.7.0 and libdap-3-7-8 from the rpm because 'include' and 'lib' files would be automatically built in ${DAP_ROOT}/lib64 and ${DAP_ROOT}/include/libdap and ${DAP_ROOT}/include/libnc-dap directories. I guess this makes a problem for building NCO with OpenDAP because it doesn't find the good lib files which are contained in the ${DAP_ROOT}/lib64 directory and not in the expected ${DAP_ROOT}/lib directory. So, I guess the only solution is to build libdap and libnc-dap manually.
3) For more general instructions, the opendap.sh script clearly shows the good way to build NCO/OpenDAP enabled... Just few problems of compatibility between Debian commands (used in the script I think), and Fedora commands which are not exactly the same...
4) Finally, I just remark that command lines for testing the NCO ability with OpenDAP (ncks -p http://dust.ess.uci.edu/cgi-bin/dods/nph-dods/dodsdata -l . in.nc) seems not to work but works when I tried with my study examples (ncks -p http://ensemblesrt3.dmi.dk/cgi-bin/nph-dods/data/prudence/daily/SMHI/HCA2/ -l . LWdown.SMHI.HCA2.nc.gz)! So Charlie, maybe you could check the examples given in the NCO guide...
To resume:
cd ${DATA}/tmp
wget ftp://ftp.unidata.ucar.edu/pub/opendap/source/libdap-3.7.8.tar.gz
wget ftp://ftp.unidata.ucar.edu/pub/opendap/source/libnc-dap-3.7.0.tar.gz
wget http://dust.ess.uci.edu/nco/src/nco-3.9.2.tar.gz
tar xvzf libdap-3.7.8.tar.gz
tar xvzf libnc-dap-3.7.0.tar.gz
tar xvzf nco-3.9.2.tar.gz
export DAP_ROOT='/usr/local'
sudo /bin/rm -r ${DAP_ROOT}/include/libdap ${DAP_ROOT}/include/libnc-dap
sudo /bin/rm ${DAP_ROOT}/lib/libdap* ${DAP_ROOT}/lib/libnc-dap*
cd ${DATA}/tmp/libdap-3.7.8
CXX='g++' ./configure --prefix=${DAP_ROOT}
make
sudo make install
cd ${DATA}/tmp/libnc-dap-3.7.0
CXX='g++' ./configure --prefix=${DAP_ROOT}
make
sudo make install
cd ${DATA}/tmp/nco-3.9.2
CXX='g++' ./configure
make
sudo make install
Hi,
Thanks for the feedback.
> > 2) Be aware not to install libnc-dap-3.7.0 and libdap-3-7-8 from the
rpm because
> > 'include' and 'lib' files would be automatically built in
${DAP_ROOT}/lib64
> > and ${DAP_ROOT}/include/libdap and ${DAP_ROOT}/include/libnc-dap
directories.
> > I guess this makes a problem for building NCO with OpenDAP because it
doesn't
> > find the good lib files which are contained in the ${DAP_ROOT}/lib64
directory
> > and not in the expected ${DAP_ROOT}/lib directory. So, I guess the
only solution
> > is to build libdap and libnc-dap manually.
The NCO FC6 RPMs we distribute are built with stock DAP RPMs.
We do not have an FC7 machine. Is there a way to automatically
update from FC6 to FC7?
> > 4) Finally, I just remark that command lines for testing the NCO ability with
> > OpenDAP (ncks -p http://dust.ess.uci.edu/cgi-bin/dods/nph-dods/dodsdata -l .
> > in.nc) seems not to work but works when I tried with my study examples (ncks
> > -p http://ensemblesrt3.dmi.dk/cgi-bin/nph-dods/data/prudence/daily/SMHI/HCA2/
> > -l . LWdown.SMHI.HCA2.nc.gz)! So Charlie, maybe you could check the examples
> > given in the NCO guide...
This is our fault. Daniel, will you please configure the DAP server on
dust.ess.uci.edu to automatically restart after reboots?
Your manual build procedure is very elegant! Usually scripts like that
only work in books :)
Hi,
> The NCO FC6 RPMs we distribute are built with stock DAP RPMs.
> We do not have an FC7 machine. Is there a way to automatically
> update from FC6 to FC7?
There is. You can use the Fedora equivalent of the Debian apt-get dist-upgrade method, which works a little less seamlessly in the Fedora world, or the install cd's upgrade function, which is the recommended way. Is there a machine you wanted upgraded?
> This is our fault. Daniel, will you please configure the DAP server on
> dust.ess.uci.edu to automatically restart after reboots?
Oh, sorry about that! We forgot to reinstall DAP after its drive crashed. I don't know how we missed it until now. I'm re-doing it now.
-Daniel
> You can use the Fedora equivalent of the Debian apt-get dist-upgrade method, which works a little less seamlessly in the Fedora world
What is the exact command?
> Is there a machine you wanted upgraded?
soot.ess.uci.edu
> Oh, sorry about that! We forgot to reinstall DAP after its drive crashed. I don't know how we missed it until now. I'm re-doing it now.
Thanks!
>> You can use the Fedora equivalent of the Debian apt-get dist-upgrade method, which works a little less seamlessly in the Fedora world
> What is the exact command?
Basically:
# make things spic-n-span before starting
sudo yum clean all
# change the release (kind of like changing your /etc/apt/sources.list)
sudo rpm -Uhv ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/Fedora/fedora-release-*.noarch.rpm
# apply the upgrade
sudo yum upgrade
There might be a few gotchas, so you'll want to skim http://fedoraproject.org/wiki/YumUpgradeFaq before you start.
FYI: dust seems running with Opendap now.
As an aside, VMWare is great for this sort of thing-- I've got images of Fedora 7, Nexenta/Solaris10, and CentOS5 on tephra.
-Daniel
FYI I have built and tested FC7 RPMs for i386.
They were built with the FC7 DAP RPMs and work with the
test cases in the manual (thanks to Daniel).
They are available at
http://nco.sf.net#fc
Havn't build x86_64 with FC7 yet, but I think they should
build fine from the source RPMs.
Charlie