> > I tried setting the LIBS variable to "-lc" on the command line (while > > removing it from the LDFLAGS variable) and that worked for the initial > > configure but failed if I did ./config-status --recheck because the > > LIBS varible was not saved and re-set (though CFLAGS and LDFLAGS were). > > That sounds like a bug. The LIBS variable is not mentioned in the output of "./configure --help", nor is there any code in the "configure" script to note that it had a environment value when the program started. The script does make use of any pre-existing value, prexfixing any new library it wants to test. How's this for a better description... The scripts generated by "autoconf" will make use of any existing LIBS environment variable in much the same way as CFLAGS and LDFLAGS are used. When doing tests for libraries, the lib being tested is prefixed to that variable and the test made. However, the value of the LIBS envionment variable is not saved in the "config.status" file to be used again when "./config.status --recheck" is run. Thus, it is possible to have it configure correctly the first time but not when it is re-checked. Brian ( bcwhite@xxxxxxxxxxxx ) ------------------------------------------------------------------------------- He who has infinite patience sees instant results.