Joe Buck <[EMAIL PROTECTED]> writes: > But ia64-unknown-linux-gnu/libgcc/config.log doesn't have any useful > details. It has > > CC='/remote/atg5/jbuck/gcc-4.3.2-ia64build/./gcc/xgcc > -B/remote/atg5/jbuck/gcc-4.3.2-ia64build/./gcc/ > -B/u/jbuck/cvs.ia64/4.3.2/ia64-unknown-linux-gnu/bin/ > -B/u/jbuck/cvs.ia64/4.3.2/ia64-unknown-linux-gnu/lib/ -isystem > /u/jbuck/cvs.ia64/4.3.2/ia64-unknown-linux-gnu/include -isystem > /u/jbuck/cvs.ia64/4.3.2/ia64-unknown-linux-gnu/sys-include' > > and ends with > > ------------- > #define PACKAGE_BUGREPORT "" > #define PACKAGE_NAME "GNU C Runtime Library" > #define PACKAGE_STRING "GNU C Runtime Library 1.0" > #define PACKAGE_TARNAME "libgcc" > #define PACKAGE_VERSION "1.0" > > configure: exit 1 > ------------- > > and the "exit 1" is the only sign that something is wrong.
These days autoconf likes to dump a whole bunch of cruft at the end of config.log. You have to look above all the cruft, which is usually most of the file, to find the actual failing test case. Ian
