[CentOS] scary messages from autoconf
hennebry at web.cs.ndsu.nodak.edu
Tue Nov 27 18:17:07 UTC 2012
On Tue, 27 Nov 2012, m.roth at 5-cent.us wrote:
> Michael Hennebry wrote:
>> 'Twould be nice just to know what the messages mean.
>> I get the impression that output like this are indications of a problem
>> 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
>>> 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
>> usable, not present, accepted by the compiler, rejected by the
> Here's a question: *which* limits.h? On my 6.3 system, if I locate
> limits.h, I get:
Don't know for sure.
I have even more.
>From experiment, gcc and cpp search the same directories:
/usr/local/include does not have a limits.h .
has a #include_next <limits.h> that grabs /usr/include/limits.h .
Michael hennebry at web.cs.ndsu.NoDak.edu
"On Monday, I'm gonna have to tell my kindergarten class,
whom I teach not to run with scissors,
that my fiance ran me through with a broadsword." -- Lily
More information about the CentOS