[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[netCDF #PRG-103154]: pgCC error, libtool, instantiation_dir
- Subject: [netCDF #PRG-103154]: pgCC error, libtool, instantiation_dir
- Date: Mon, 08 Feb 2010 13:22:29 -0700
Hi Kodi,
> The 4.1 release gave me the same error (see below).
>
> ./configure
> configure: netCDF 4.1
> checking build system type... x86_64-unknown-linux-gnu
...
> make[2]: Leaving directory `/home/knemunai/netcdf-4.0.1/nf_test'
> Making all in cxx
> make[2]: Entering directory `/home/knemunai/netcdf-4.0.1/cxx'
> source='netcdf.cpp' object='netcdf.lo' libtool=yes \
> DEPDIR=.deps depmode=none /bin/sh ../depcomp \
> /bin/sh ../libtool --tag=CXX --mode=compile pgCC -DHAVE_CONFIG_H
> -I. -I.. -I..> /fortran -I../libsrc -fastsse -tp core2-64 -c -o
> netcdf.lo netc> df.cpp
> libtool: compile: pgCC -DHAVE_CONFIG_H -I. -I.. -I../fortran
> -I../libsrc -fast> sse -tp core2-64 -c netcdf.cpp -o netcdf.o
> source='ncvalues.cpp' object='ncvalues.lo' libtool=yes \
> DEPDIR=.deps depmode=none /bin/sh ../depcomp \
> /bin/sh ../libtool --tag=CXX --mode=compile pgCC -DHAVE_CONFIG_H
> -I. -I.. -I..> /fortran -I../libsrc -fastsse -tp core2-64 -c -o
> ncvalues.lo nc> values.cpp
> libtool: compile: pgCC -DHAVE_CONFIG_H -I. -I.. -I../fortran
> -I../libsrc -fast> sse -tp core2-64 -c ncvalues.cpp -o ncvalues.o
> /bin/sh ../libtool --tag=CXX --mode=link pgCC -fastsse -tp core2-64
> -version-i> nfo 4:0:0 -o libnetcdf_c++.la -rpath
> /home/knemunai/netcdf/pgi/4.0> .1/non_mpi/lib netcdf.lo ncvalues.lo
> ../libsrc/> libnetcdf.la
> libtool: link: tpldir=Template.dir
> libtool: link: rm -rf Template.dir
> libtool: link: pgCC --prelink_objects --instantiation_dir
> Template.dir netcdf.> o ncvalues.o
> pgCC-Error-Unknown switch: --instantiation_dir
> make[2]: *** [libnetcdf_c++.la] Error 1
> make[2]: Leaving directory `/home/knemunai/netcdf-4.0.1/cxx'
The above error message is a symptom of a bug in libtool where it's
treating PGI version "10.0" as version "1.0", according to:
http://www.pgroup.com/userforum/viewtopic.php?t=1736&sid=89ca6aca8becc5cdf3ae34c4de6a519a
One way to work around the problem is to just not build and test the
C++ netCDF interface, by setting the environment variable CXX=''
before running the configure script. Nothing else in the netCDF
distribution depends on the C++ API, so that should be OK unless you
have users of the C++ API.
--Russ
Russ Rew UCAR Unidata Program
address@hidden http://www.unidata.ucar.edu
Ticket Details
===================
Ticket ID: PRG-103154
Department: Support netCDF
Priority: Normal
Status: Closed