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

20030130: ./configure not successful; redirecting standard error

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: 20030130: ./configure not successful; redirecting standard error
  • Date: Thu, 30 Jan 2003 09:06:00 -0700
Youlong,

>Date: Thu, 30 Jan 2003 09:50:45 -0600 (CST)
>From: Youlong Xia <address@hidden>
>Organization: University of Texaas
>To: address@hidden
>Subject: Re: ./configure not successful 

The above message contained the following:

> >> when I re-execute the configure script.  Redirect its standard output
> >>         and standard error to the file "configure.log".  This step
> >>         fails -- which is indicated by error messages (not warnings) in
> >>         "configure.log" . configure.log is:
> >
> >What package are you attempting to build?  Possibilities are
> >
> >    netCDF
> >    UDUNITS
> >    LDM
> >    netcdf-perl
> >
> I want to build netCDF, thanks,

Thanks.

The file that you sent me was the file "config.log" -- which is created
directly by the configure script -- rather than the file "configure.log"
-- which is created by redirecting the standard output and standard
error of the configure script when you execute it.

Please send me the file "configure.log". Please ensure that it contains
the standard error of the configure script. The mechanism for doing this
depends on your user-shell, e.g.,

    Standard shell (e.g., sh, ksh, bash):

        ... ./configure ... >configure.log 2>&1

    csh-like shell (e.g., csh, tcsh):

        ./configure ... >&!configure.log

where "..." denotes optional stuff.

The "configure.log" file is also described near the end of the file
INSTALL.html.

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