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

[netCDF #WQQ-808975]: make check 1 test failed

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 #WQQ-808975]: make check 1 test failed
  • Date: Sun, 19 Oct 2008 16:24:40 -0600
Hi Guziy,

It looks like you are following Intel's recommended configure settings for
netCDF version 3.6.2,
but you haven't said what platform you are using or whether you are using
netCDF 3.6.3, 4.0,
or a later daily snapshot version.  The Intel site says:

  Note that the -xT compiler option will generate code using SSE3 instructions
  that are not
  available on processors older than Intel Core 2 Duo processors. If you will
  be using the
  libraries on systems with older Intel processors, you will want to use the
  xP, -xN, or xW
  options. Consult the online compiler documentation installed with the
  compiler for details
  about these options.

Are you trying to build on an processor older than the Intel Core 2 Duo
processors, such as the
Intel Core Duo processor?  If so, it may help to not use the -xT option.

We have examples of successful builds on Linux with Intel 10.1 compilers and
the current netCDF
daily snapshot for both 32-bit and 64-bit builds here:

  Intel 10.1, 32-bit    CC=icc CXX=icpc FC=ifort F77=ifort
     
http://www.unidata.ucar.edu/netcdf/builds/snapshot/out_shecky_2008101610_3_0.txt
  Intel 10.1, 64-bit    CC=icc CXX=icpc FC=ifort F77=ifort
     
http://www.unidata.ucar.edu/netcdf/builds/snapshot/out_shecky_2008101610_4_0.txt

In these builds, the configure script figured out which compiler flags to use,
and it looks like
-xT was not used (if you run configure, it may find different locations for
libraries):

  checking CC CFLAGS... icc -L/opt/gcc4.1.2/lib -O3 -xN -ip -no-prec-div
  -static
  checking CXXFLAGS... -L/opt/gcc4.1.2/lib -O3 -xN -ip -no-prec-div -static
  -I/opt/gcc4.1.2/include
  checking FFLAGS... -L/opt/gcc4.1.2/lib -O3 -xN -ip -no-prec-div -static
  checking FCFLAGS... -g

So if you are using 3.6.2, 3.6.3, or 4.0 netCDF versions, it may work to just
set the compiler
flags as above.

Please let us know if this doesn't help.

--Russ




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



Ticket Details
===================
Ticket ID: WQQ-808975
Department: Support netCDF
Priority: Normal
Status: Closed