Zack Weinberg <za...@panix.com> writes: > which, as well as the desired check, does
> checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > The only tests in that list that are worth doing nowadays are for > stdint.h and inttypes.h, and I don't think they should be done > implicitly. I think you're assuming a hosted target. I'm not sure that you can make that assumption. Can't Autoconf be used to cross-compile software for a free-standing target, where several of those header files are not required to exist? -- Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
