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

[netCDF #FTM-837716]: error compiling - z library

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [netCDF #FTM-837716]: error compiling - z library
  • Date: Wed, 23 Mar 2011 20:18:01 -0600
Hi John,
> I'm trying to compile 4.1.2-rc1 w/ netcdf4/hdf5 support. configure error: 
> Can't find or link to the z library
> 
> However, the libz is available:
> [jcc@claymore netcdf-4.1.2-rc1]$ ls -al /usr/lib64/libz.*
> -rwxr-xr-x 1 root root 108692 Jul 19  2006 /usr/lib64/libz.a
> lrwxrwxrwx 1 root root     13 Mar  4 04:15 /usr/lib64/libz.so -> libz.so.1.2.3
> lrwxrwxrwx 1 root root     13 Mar  4 04:14 /usr/lib64/libz.so.1 -> 
> libz.so.1.2.3
> -rwxr-xr-x 1 root root  85928 Jul 19  2006 /usr/lib64/libz.so.1.2.3
> 
> and I thought my configuration specified it's location:
> export CFLAGS="-I/usr/include -L/usr/lib64"
> export LDFLAGS="-L/usr/lib64"
> export LIBS="-lz"
> 
> ./configure \
> --prefix=/home/jcc/contrib/netcdf-4.1.2 \
> --enable-netcdf-4 \
> --enable-cxx-4 \
> --enable-extra-example-tests \
> --disable-dap \
> --enable-cdmremote \
> --disable-dap-remote-tests \
> --disable-examples \
> --disable-fortran \
> --with-udunits \
> --with-hdf5 \
> --with-zlib

Just a guess, but it's possible that either you're trying to compile in the 
32-bit model (in
which case the lib64 library would not be usable, even though you explicitly 
specify to look
there).  Make sure you either specify -m64 as a compiler/linker flag or that 
the default for
the compiler you're using is 64-bit.

Another possibility is that a 32-bit libz shared library is installed in the 
path that your system
is configured to search, and it's looking instead for a 64-bit library.  You 
could use ldconfig(8) to
set the load paths correctly in /etc/ld.so.conf for Linux systems or the 
equivalent for other
platforms.  Also you could test if its a shared library path problem by seeing 
if setting
LD_LIBRARY_PATH to a directory containing the library for the right bitlength 
model makes
things work as expected.

--Russ

Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: FTM-837716
Department: Support netCDF
Priority: Normal
Status: Closed