On Tue, 27 Nov 2012, m.roth@5-cent.us wrote:
Michael Hennebry wrote:
<snip> > 'Twould be nice just to know what the messages mean. > I get the impression that output like this are indications of a problem > that > is not specific to the particular software that I was trying to compile: > autoconf wrote: >> checking for stdint.h... (cached) yes >> checking limits.h usability... yes >> checking limits.h presence... no >> configure: WARNING: limits.h: accepted by the compiler, rejected by the >> preprocessor! >> configure: WARNING: limits.h: proceeding with the compiler's result >> checking for limits.h... yes >> checking for unistd.h... (cached) yes >> checking sys/time.h usability... yes > > limits.h: > usable, not present, accepted by the compiler, rejected by the > preprocessor. > > Huh?
Here's a question: *which* limits.h? On my 6.3 system, if I locate limits.h, I get: /usr/include/limits.h /usr/include/c++/4.4.4/tr1/limits.h /usr/include/linux/limits.h /usr/lib/gcc/x86_64-redhat-linux/4.4.4/include/limits.h /usr/lib/gcc/x86_64-redhat-linux/4.4.4/include/syslimits.h /usr/share/doc/pam-1.1.1/html/sag-pam_limits.html /usr/share/man/man0p/limits.h.0p.gz /usr/src/kernels/2.6.32-279.1.1.el6.x86_64/include/linux/limits.h /usr/src/kernels/2.6.32-279.11.1.el6.x86_64/include/linux/limits.h /usr/src/kernels/2.6.32-279.2.1.el6.x86_64/include/linux/limits.h /usr/src/kernels/2.6.32-279.5.2.el6.x86_64/include/linux/limits.h /usr/src/kernels/2.6.32-279.9.1.el6.x86_64/include/linux/limits.h
Don't know for sure. I have even more.
From experiment, gcc and cpp search the same directories:
/usr/local/include /usr/lib/gcc/i686-redhat-linux/4.4.6/include /usr/include
/usr/local/include does not have a limits.h . /usr/lib/gcc/i686-redhat-linux/4.4.6/include/limits.h has a #include_next <limits.h> that grabs /usr/include/limits.h .