[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
951005: netCDF on sun solaris
- Subject: 951005: netCDF on sun solaris
- Date: Thu, 05 Oct 95 15:07:38 -0600
Cindy,
> Subject: netCDF on sun solaris
> To: address@hidden
> From: address@hidden (CR Turney)
> Organization: Battelle Pacific Northwest Laboratories
> >Keywords: 199510051709.AA26566
In the above message you wrote:
> I am having difficulties creating a tested netcdf library.
>
> I am working on a Sun Sparc running SunOS 5.4 (solaris). I am
> using gcc-2.6.3, a Sun provided fortran compiler (f77-3.0.1), and
> netcdf-232pl4.
>
> I ran configure and make all without apparent problems. When I
> attempt a "make test" xdrtest and cdftest are successful, but nctest has
> many failures and finally core dumps.
>
> Can you help me? More info follows, see below.
>
> Cindy Turney
> Battelle Pacific Northwest Laboratories
> (509) 375-2175
> address@hidden
>
>
> My CUSTOMIZE file follows:
>
> # This file is for customizing the configuation process performed by
> # `./configuration'. This file consists of sh(1) variable-definition lines.
> # The value given to those variables by this file will override their default
> # values.
> #
> # You can also customize the configuration process via the environment
> # variables seen by ./configure. For example:
> #
> # In csh(1):
> # % setenv CC acc
> # & setenv CFLAGS -g
> # % ./configure
> #
> # In sh(1):
> # $ CC=acc CFLAGS=-g ./configure
> #
> # Variables in this file override the environmental ones.
> #
> #############################################################################
> #
> # Type of C compiler (default is `cc'):
> CC='gcc'
> FC=f77
> #
> # C compiler flags (default is `-O'):
> CFLAGS=-g
> #
> # C preprocessor flags (default is `-DNDEBUG'):
> CPPFLAGS='-DDEBUG -DXDRSTDIO'
> XDRFILE=xdrstdio
I suggest the following:
1. In file CUSTOMIZE, remove the -DXDRSTDIO from CPPFLAGS and don't
set XDRFILE.
2. Execute a `make clean'.
3. Re-execute the configure script. Trap the output and send it to
me if a problem occurs.
4. Re-execute a `make clean'. Trap the output and send it to me if
a problem occurs.
5. Re-execute a `make test'. Trap the output and send it to me if
a problem occurs.
--------
Steve Emmerson <address@hidden>