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

Re: 19990830: trouble at configure

Dear Shin Miyazaki,

>Date: Tue, 31 Aug 1999 10:56:01 +0900
>From: Shin MIYAZAKI <address@hidden>
>Organization: .
>To: Steve Emmerson <address@hidden>
>Subject: Re: 19990830: trouble at configure
>Keywords: 199908301020.EAA02218

In the above message, you wrote:

>     D.  The file "configure.log" from step 6 above.
> 
> confirure.log is as follows.
> 
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> configure:1020: /usr/bin/cc -c -O -DNDEBUG conftest.c 1>&5
> configure:1153: CC -c  -DNDEBUG conftest.C 1>&5
> configure:1220: /usr/bin/cc -E -DNDEBUG conftest.c >/dev/null 2>conftest.out
...

The above is the file "config.log" rather than the file "configure.log"
from step 6 of the installation process.  The names are similar and can
be confused.

File "configure.log" from step 6 in the installation process contains
the standard output and standard error from executing the configure
script and should start with somthing like the following:

    creating cache ./config.cache
    checking for m4... m4
    checking user-defined C compiler "/opt/SUNWspro/bin/c89"
    checking C compiler... works
    checking how to make dependencies... cc -xM
    checking for /opt/SUNWspro/bin/CC... /opt/SUNWspro/bin/CC
    checking C++ compiler "/opt/SUNWspro/bin/CC"... works
    checking how to run the C preprocessor... /opt/SUNWspro/bin/c89 -E
    checking user-defined Fortran compiler "/opt/SUNWspro/bin/f77"... works
    checking for Fortran .F compiler... 
    ...

Would you please send me this file.

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