The first test looks for a typedef in the headers; the second, for a
compiler built-in (like int). I suppose one thing thats not looked for is
a #define in the headers. I suppose one thing thats still not covered is a
#define in the header - that wouldn't show up in the cpp output, nor would
the compilaton work. How is ulong defined in sys/bsd_types? Does cc -c
work on:
#include "confdefs.h"
#include <sys/types.h>
#if STDC_HEADERS
#include <stdlib.h>
#include <stddef.h>
#endif
int main() {
ulong foo;
; return 0; }
Greg
Richard Gillilan <[EMAIL PROTECTED]>@opendx.watson.ibm.com on
06/19/2000 04:21:48 PM
Please respond to [email protected]
Sent by: [EMAIL PROTECTED]
To: [email protected]
cc:
Subject: [opendx-dev] IRIX: debugging configure
> confdefs.h is a list of definitions found in earlier tests. So run the
cpp
> statement. Either it will simply failing, so no output to stdout is
> produced,
> or utype just isn't there, in which case thats the problem and stderr
will
> tell you a lot about whats going on.
>
> If the preprocessor didn't fail and utype just isn't in the output, then
> the compilation test kicks in.
Yep, the preprocessor just spits the same thing back out again, sothe next
test
is performed.
> It tries the compile statement on:
>
> #include "confdefs.h"
>
> int main() {
> ulong foo;
> ; return 0; }
>
> and thats failing; again stderr will tell you why.
The compilation options are simply "cc -c"
The second test fails because ulong is not yet defined in
confdefs.h, so the compilation has trouble with type
ulong.
I don't see the point of this test except to determine if the ulong
definition is in confdefs.h or not. Somewhere, configure should be
testing to see if ulong is defined eslewhere. It occurs in sys/bsd_types
which
is included in sys/types.h. sys/types.h is in unistd.h and many other
includes.
Richard
