Hello John, Apologies for the delay, and thanks for your bug report on config.guess. * John Wohlbier wrote on Tue, Jul 25, 2006 at 04:12:57PM CEST: > Below are comments from a sysadmin as to why config.guess is > failing for me. Below that is the original problem statement, > and below that is the config.guess script. Is config.guess "wrong?" Yes, it was wrong; but that has since been fixed. Up-to-date versions of the two files in question can be found at http://cvs.savannah.gnu.org/viewcvs/~checkout~/config/config/config.guess http://cvs.savannah.gnu.org/viewcvs/~checkout~/config/config/config.sub Please note that Autoconf is not in charge of the files, but config-patches@xxxxxxx is. > This has to do with the difference from the output from the pgi and gcc > preprocessors. The script looks for output of the form "LIBC=something" > from a C preprocessor, but does not account for the possibility that the > output might have spaces between LIBC and the = sign. > > If you rearrange line 190 from: > > eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep LIBC= | sed -e 's: ::g'` > > to: > > eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | sed -e 's: ::g' | grep LIBC=` > > it should work as expected. This removes the spaces from the output > BEFORE grepping for the LIBC content. Cheers, Ralf _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
