"Peter Kovacs" <[EMAIL PROTECTED]> writes:
> bash-3.00# uname -a
> HP-UX apollo B.11.23 U ia64 1874023332 unlimited-user license
> I got the following warnings:
> checking sys/ipc.h presence... yes
> configure: WARNING: sys/ipc.h: present but cannot be compiled
Which compiler are you using? If gcc, is it up-to-date? The main cause
I've seen of these types of warnings on HP-UX is using a gcc that was
originally built on an older HP-UX version and has obsolete copies of
system header files embedded in it. HP themselves seem to lack a clue
or three in this department, as the gcc currently installed on their
TestDrive machines fails exactly this way.
For reference, the way to check this out is to look at "gcc -v" output
to see where its private files are, for instance it'll say something like
Reading specs from /usr/local/lib/gcc/ia64-hp-hpux11.23/3.4.3/specs
Then you look under
/usr/local/lib/gcc/ia64-hp-hpux11.23/3.4.3/include
and compare the files there to the equivalent files in /usr/include.
The proximate cause of the immediate problem on the TestDrive
machine is found by comparing
diff /usr/local/lib/gcc/ia64-hp-hpux11.23/3.4.3/include/sys/types.h
/usr/include/sys/types.h
which shows that gcc's version is lacking a definition for cid_t,
which is the exact problem complained of when you look into our
config.log to find out *why* sys/ipc.h doesn't compile.
Or, to make a long story short:
$ cat test.c
#include <sys/types.h>
#include <sys/ipc.h>
$ gcc test.c
In file included from test.c:2:
/usr/include/sys/ipc.h:51: error: parse error before "cid_t"
/usr/include/sys/ipc.h:56: error: parse error before '}' token
$
Feel free to try to get HP's attention about this; not being a paying
customer any more, I don't seem to have any useful contacts. In the
meantime, use their cc, or build gcc for yourself so it's up to date.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
