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

Re: 980415: problems building netCDF 3.4 under HPUX 10.20

Gregg,

>Date: Wed, 15 Apr 1998 14:49:49 -0600 
>From: Gregg Phillips <address@hidden>
>Organization: NOAA/ERL/FSL/MD Boulder, CO 
>To: Steve Emmerson <address@hidden>
>Subject: Re: 980415: problems building netCDF 3.4 under HPUX 10.20 
>Keywords: 199804151618.KAA15463 netCDF 3.4 build

In the above message, you wrote:

> The VERSION file does contain the string 3.4. I was wondering if
> it might be a path issue. Would you mind sending output from echo
> $PATH? Mine looks like the following:
> 
> hal /tmphome/src/netcdf-3.4/src 70 > echo $PATH
> /usr/local/tcl/bin:/usr/local/tk/bin:/opt/ansic/bin:/opt/langtools/bin:/usr/sbin:/usr/etc:/usr/bin:/usr/local/bin:/usr/bin/X11:/etc:/bin:/home/hal/phillips/bin:.
> 

Interesting.  You have "/opt/ansic/bin" in your path and I don't:

    $ echo $PATH
    /usr/local/gnu/bin:/usr/opt/posix/usr/bin:/home/steve/bin:/bin:/usr/sbin:/u
sr/ccs/bin:/usr/bin:/usr/ucb:/sbin:/upc/share/JavaCC/bin:/local/bin/X11:/local/
bin/X11:/usr/bin/mh:/bin/X11:/usr/bin/X11:/local/gnu/bin:/local/bin:/usr/local/
bin:/local/etc:/upc/netcdf/bin:/upc/ncopers/bin:/upc/ldm-mcidas/bin:/upc/udunit
s/bin:/local/ldm/bin:/upc/xgks/bin:/etc

Looking over the previous output from you configure script, it appears
that your setting of the following environment variables:

    CC=/bin/c89
    CPPFLAGS="-D_HPUX_SOURCE -DNDEBUG"
    CFLAGS=-O
    FC=/opt/fortran/bin/fort77          # might be /usr/bin/fort77 instead
    FFLAGS="-O3 -w"
    CXX=/usr/bin/CC

didn't "take".  Your execution of the configure script emitted the following
output:

    creating cache ./config.cache
    checking for m4... m4
    checking for xlc... no
    checking for c89... c89

whereas my execution emmitted the following:

    creating cache ./config.cache
    checking for m4... m4
    checking user-defined C compiler "/bin/c89"

I suspect that the environment variable CC wasn't set -- and the same for
the other environment variables.

Would you please do the following:

    1.  Go to the top-level source directory.

    2.  Execute the commmand "make distclean".

    3.  Remove the file "config.cache" if it exists.

    4.  Set the above environment variables to the indicated values.

    5.  Execute the command "env" and check to see that the above
        environment variables are, indeed, set to the correct values.

    6.  Execute the configure script.  Redirect both standard output and
        standard error to the file "configure.log".  Send me the file.

--------
Steve Emmerson   <http://www.unidata.ucar.edu>