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

20030110: netCDF library link problem: missing f77 interface

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: 20030110: netCDF library link problem: missing f77 interface
  • Date: Fri, 10 Jan 2003 13:11:55 -0700
Ashish,

>Date: Fri, 10 Jan 2003 14:37:40 -0500
>From: ashish arora <address@hidden>
>Organization: University of Kent
>To: Steve Emmerson <address@hidden>
>Subject: RE: 20030109: netCDF library link problem: missing f77 interface

The above message contained the following:

> Step A: Which is exection of command "uname -a" provides us the following 
> output.
>  
> Linux snowy 2.4.18-3smp #1 SMP Thu Apr 18 07:27:31 EDT 2002 i686 unknown
>  
> Step D:"Configure.log":Please tell me which log file is generated when we run 
> configure script.I am confused about how to create configure.log.

The file "configure.log" is created by you when you redirect the
standard output and standard error of the "configure" script to that
file. The exact way to do this depends on what type of user-shell you
are using. If you are using a csh-like user-shell (e.g. "csh", "tcsh")
then the following command should work:

    ./configure >&! configure.log

if, however, you are using a standard shell (e.g. "sh", "ksh", "bash"),
then the following command should work:

    ./configure >configure.log 2>&1

...
> Thanx 
> Ashish Arora

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