From: Jason K. <jas...@ua...> - 2002-04-06 00:39:33
|
On Friday, April 5, 2002, at 02:44 PM, Martin Costabel wrote: Jason Knight wrote: [] If configure does the wrong thing, check the file config.log for information that may help you understand what went wrong. Did you try to follow this advice? -- Martin :) As I said, I'm a bear of little brain when it comes to much of this. I did look but couldn't make much sense of it. Here it is: Fri Apr 5 12:14:22 AKST 2002 Running ./configure with arguments: --noninteractive This file contains information that is captured from running the configure script. Lines that begin with a "+" are command lines echoed by the shell. Other lines are the output of commands; usually the contents of test case files or the output from compilers. If configure does the wrong thing, you can use the information captured here to aid in debugging. + . ./config.site + PREFIX=/sw + DSO=auto + JPEG=yes + ZIP=yes + DIR_BIN=/sw/bin + DIR_LIB=/sw/lib + DIR_INC=/sw/include + DIR_MAN=/sw/share/man + DIRS_LIBINC= /sw/include /sw/include /sw/include + DIR_JPEGLIB=/sw/lib + DIRS_LIBINC= /sw/include /sw/include /sw/include /sw/include + DIR_GZLIB=/sw/lib + cat dummy.c main(int argc, char* argv) { exit(0); } + cat xgnu.c #ifdef __GNUC__ yes; #endif + gcc -E xgnu.c capture: command not found: gcc [2] + egrep yes + gcc -o dummy dummy.c capture: command not found: gcc [2] + cat xgnu.c #ifdef __GNUC__ yes; #endif + cc -E xgnu.c + egrep yes yes ; + cc -o dummy dummy.c As for Alexander's question, jason% which cc /usr/bin/cc Thanks, folks! Jason |