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

Re: RUN_script

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: Re: RUN_script
  • Date: Tue, 21 Dec 2004 10:25:49 -0700
T. W. Tesche,

>Date: Tue, 21 Dec 2004 12:16:36 -0500
>From: "T. W. Tesche" <address@hidden>
>Organization: Alpine Geophysics, LLC
>To: "Emmerson, Steve" <address@hidden>
>Subject: RUN_script
> Keywords: 200412211526.iBLFQDgJ001714 netCDF 3.5.1 RedHat Linux 9

The above message contained the following:

> Steve:  Sorry, I forgot the RUN_script.  Here it is.
> 
> twt
...
> # !/bin/csh
> 
> rm *.log
> 
> #setenv FFLAGS '-O2 -Mfixed -Mextend'                    # caused make test 
> to fail
> #setenv FFLAGS ' '                                       # make test ok, but 
> make install failed
> #setenv FFLAGS '-O'                                      # make test ok, but 
> make install failed
> setenv CXX /usr/bin/g++
> setenv CC /usr/bin/gcc
> setenv CFLAGS '-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE'
> setenv CPPFLAGS '-DNDEBUG -DpgiFortran'
> setenv FC /usr/pgi/linux86/5.2/bin/pgf90
> #setenv F77 /usr/pgi/linux86/5.2/bin/pgf90
> setenv F90 /usr/pgi/linux86/5.2/bin/pgf90
> ./configure 
> #
> make clean 
> make all >& make.log &
> make test >& test.log &
> make install >& install.log &

Executing all the above make(1)s asynchronously (i.e., in the
background) is not a good idea because they'll step all over each other.

It would be better to do the following

    make clean 
    make all >& make.log
    make test >& test.log
    make install >& install.log

Regards,
Steve Emmerson