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

20030305: using g++ 3.2 to build netCDF (cont.)

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: 20030305: using g++ 3.2 to build netCDF (cont.)
  • Date: Sat, 08 Mar 2003 10:02:55 -0700
>From: Mike Dixon <address@hidden>
>Organization: NCAR/RAP
>Keywords: 200303051637.h25GbC315003 netCDF g++ 3.2

Hi Mike,

>Thanks for the quick response.

Sorry that my second response wasn't quick as well...

>I downloaded the beta code.
>
>When I run configure I still get the following, which means it will
>not build the C++ part.
>
>    30  18:43   setenv CC /usr/local/gcc-3.2.2/bin/gcc
>    31  18:43   setenv CXX /usr/local/gcc-3.2.2/bin/g++
>    32  18:43   ./configure --prefix=/home/dixon/rap
>
>    ....
>
>    checking C++ compiler "/usr/local/gcc-3.2.2/bin/g++"... configure: warning
> :
>    /usr/local/gcc-3.2.2/bin/g++ failed on standard C++ test program
>
>    ....
>
>Is it maybe just the test program which needs updating here?

'configure' creates little test programs on the fly and uses the
compiler specifed to see if they will compile.  A failure to compile
doesn't necessarily mean that there is a problem, but when configure
exits it means that there is a serious problem.

In order to figure out what is going on on your system, we will need to
see the contents of the config.log file that is generated by the
'./configure' step.  The exact problem encountered will be noted at the
point of failure in the file; this should be at or very near the end.

>Thanks again

Again, sorry I couldn't get back to you in a more timely manner.

Tom