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

970617: building netCDF on an HP-UX <something>

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: 970617: building netCDF on an HP-UX <something>
  • Date: Thu, 17 Jul 97 13:00:49 -0600
Bill,

>Date: Thu, 17 Jul 1997 13:05:33 -0400 
>From: Bill Hudson <address@hidden>
>Organization: Pennsylvania State University/Applied Research Laboratory
>To: Steve Emmerson <address@hidden>
>Subject: Re: 970617: building netCDF on an HP-UX <something> 
>Keywords: 199707151311.HAA19835

In the above message, you wrote:

>  Here are the output's:
> 
> $ FOO=bar
> $ sh -c 'echo no export: $FOO'
> no export:
> $ export FO
> $ export FOO
> $ sh -c 'echo with export: $FOO'
> with export: bar
> $ sh -c 'echo $FOO'
> bar      

Ok.  You're definitely using an sh(1)-like shell.

Try the following:

    1.  Go to the top level of the netCDF source directory.

    2.  Execute the following commands verbatim:

            make clean
            rm config.cache
            export CPPFLAGS='-DNDEBUG -D_HPUX_SOURCE'
            export CC=cc
            export CFLAGS='-O -Aa'
            export FC=
            export CXX=CC
            ./configure >configure.log 2>&1

        You might want to use the "--prefix=..." option in that last
        command.  See the file "INSTALL" for details.

    3.  Look at the file "configure.log".  If it indicates an error,
        then stop and send me the file.

    4.  Look at the CFLAGS macro in the file "macros.make".  Does it
        contain the "-Aa" option?  If not, then stop.

    5.  Execute the following command:

            make >make.log 2>&1

    6.  Look at the file "make.log".  If it indicates an error,
        then stop and send me the file.
    
    7.  Execute the following command:

            make test >test.log 2>&1

    8.  Look at the file "test.log".  If it indicates an error,
        then stop and send me the file.

    9.  Execute the following command:

            make install >install.log 2>&1

    10. Look at the file "install.log".  If it indicates an error,
        then stop and send me the file.

    11. Execute the following command:

            make clean

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