Hi,
In going over subconfigure.com I noticed some unusual things regarding
the <unistd.h> header: in my hacked up copy of subconfigure.com there
are actually two trial programs compiled and run before we even do the
test of whether a compile of a program with #include <unistd.h> will work.
Also subsequent test programs seem to #include it unconditionally,
that is the value of perl_i_unistd is never consulted when writing
out many of the programs in subconfigure.com.
In particular, this test for inttypes.h:
$!
$! Check for inttypes.h
$!
$ OS
$ WS "#ifdef __DECC
$ WS "#include <stdlib.h>
$ WS "#endif
$ WS "#include <stdio.h>
$ WS "#include <unistd.h>
$ WS "#include <inttypes.h>
$ WS "int main()
$ WS "{"
$ WS "exit(0);
$ WS "}"
$ CS
Seems to succeed with my DEC C V6.0-001 compiler if I omit the
#include <unistd.h>. Does anyone know why it is there in so
many places (try `search [.vms]subconfigure.com unistd.h` to size
things up).
Thanks.
Peter Prymmer
