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

[netCDF #RIN-798614]: NetCDF C++ Tests Fail

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 #RIN-798614]: NetCDF C++ Tests Fail
  • Date: Mon, 23 Jun 2008 07:29:56 -0600
>
> ----- Original Message -----
> From: "Unidata netCDF Support" <address@hidden>
> To: <address@hidden>
> Cc: <address@hidden>
> Sent: Sunday, June 22, 2008 10:35 PM
> Subject: [netCDF #RIN-798614]: NetCDF C++ Tests Fail
>
>
> >> Hello,
> >>
> >> we have downloaded the netCDF library from your website, and now we are
> >> trying to build it with different compilers we got on our HPC-Cluster.
> >> Unfortunately the C++ test fails with message: "C++ runtime abort
> >> internal error : static object marked for destruction more than once".
> >> We are using the version 3.6.2.
> >
> > Well that sure sounds bad, doesn't it.
> >
> > What C++ compiler are you using?
>
> Well,
>
> we are using different C++ Compiler. For example pgCC (Portland Group...),
Pathscale, Intel 32-Bit Compiler etc. The fact is: it doesn't matter how C++
compiler we are attempting to use, every built check puts out this
error-message. We also set the compiler flags to "-O2" (but I don't believe
that it matters or does it?).
>

OK, well let's pick one and get started with it.

Let me warn you that the C++ API is not know to compile everywhere, but we
should be able to get it working for you.

(You might ask your users what languages they will be programming netCDF with.
If they are not using C++, you can disable the C++ with --disable-cxx to
configure.)

Do you have g++? That is known to work.

Also, if you are using a proprietary C compiler, you probably will need to use
the matching C++ compiler. That is, if you are building with intel C, you will
want to use the intel C++ compiler as well.

You really need to know what compiler your users want, because with C++ and
Fortran you must build a different version of the library for each compiler
(because they are not compatible with each other).

Once you pick your compiler, build it like this, and send me the complete
output of the command, as well as config.log. Just paste them all in your email
reply - it's a very long email but that's OK. We're going to turn off fortran
at first and try just C and C++:

make distclean && CXX=g++ CC=gcc ./configure --disable-f77 && make check

I loved the Roman ruins in Mainz. Although I am a fan of the ancient Romans, I
didn't really realize how far North they had gone. Ich blicke der Ruinen mit
Ehrfurcht. ;-)

Thanks,

Ed

Ticket Details
===================
Ticket ID: RIN-798614
Department: Support netCDF
Priority: Normal
Status: Open