960422: help for netCDF build, OSF1 v2.1

Alex,

> To: address@hidden
> From: address@hidden (Alex Erxuan Foo)
> Subject: help for netCDF
> Organization: Ocean Science & Technology
> Keywords: 199604192247.AA12656

In the above message you wrote:

> I am installing your netCDF on my DEC alpha OSF1 2.1 (250) computer.

You have an old version of the operating system.  This might make
support difficult.

> There is some problems. So I am asking from your help.
> 
> 1.  Here is my file CUSTOMIZE:
> #############################################################################
> #
> # C compiler (default is `cc'):
> # CC=gcc
> #
> # C compiler flags (default is `-O'):
> # CFLAGS=-g
> #
> # C preprocessor flags (default is empty):
> # CPPFLAGS=-DDEBUG
> #
> # C++ compiler (default is system-dependent).  Define as the empty 
> # string to avoid building the C++ interface.
> CXX=""
> #
> # Installation prefix (default is `..'):
> prefix=/usr/local
> # Specify f77 flags -- Alex E. Foo
> FFLAGS="-O -convert big_endian"
> 

This looks Ok.

> 2.   Then I did the following:
>     configure --prefix=/usr/local
> 
> 3.   Here is the log file:
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> /usr/lib/cmplrs/cc/cfe: Error: configure, line 2231: redeclaration of 
> 'malloc'; 
> previous declaration at line 147 in file '/usr/include/stdlib.h'
>             extern struct {int a; int b;} *malloc();
>         -----------------------------------^
> /usr/lib/cmplrs/cc/cfe: Error: configure, line 2231: Incompatible function 
> retur
> n type for this function
>             extern struct {int a; int b;} *malloc();
>         -----------------------------------------^
> 

The above isn't the log file of the configure script.  That was written
to standard output.  What you've shown is the standard error output from
compilations that the configure script ran in order to determine certain
features of the operating system.

> 
> Do you think that means I failed to build the a makefile? Do I need to
> continue the next step "make all>&! log &" ?

I would need to see the output from the configure script in order to
answer this question.

You can trap the output from the configure script in the following way
-- depending on which shell you use:

    csh:

        ./configure >&! configure.log

    sh, ksh:

        ./configure >configure.log 2>&1

    bash:

        ./configure &>configure.log

If you want an answer to your question, then I suggest you execute the
appropriate command from the above and send me the `configure.log' file.

--------
Steve Emmerson   <address@hidden>