Reading config.log
Jump to navigation
Jump to search
config.log is the logfile for configure, which is a very long shell script. When this script fails in unusual ways, it becomes necessary to look into config.log. The file is in several sections:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
....
## --------- ##
## Platform. ##
## --------- ##
hostname = euclid
....
## ----------- ##
## Core tests. ##
## ----------- ##
configure:2815: checking build system type
configure:2833: result: x86_64-unknown-linux-gnu
...
## ---------------- ##
## Cache variables. ##
## ---------------- ##
ac_cv_build=x86_64-unknown-linux-gnu
ac_cv_c_bigendian=no
ac_cv_c_compiler_gnu=yes
....
## ----------------- ##
## Output variables. ##
## ----------------- ##
ACLOCAL='${SHELL} /A/b/config/missing --run aclocal-1.10'
AIX_BACKUP=''
....
## ----------- ##
## confdefs.h. ##
## ----------- ##
#define PACKAGE_NAME ""
#define PACKAGE_TARNAME ""
....
The interesting material for a failure is usually at the end of "Core tests," so use your editor to look for "Cache variables" and then scroll upward, just as you would scroll upward from the end of any log file.