🚀 go-pugleaf

hvaisane@cs.joensuu.fi (H. Vaisanen) writes:
>I am using gcc version 2.2.2 in DECstation 3100 under Ultrix V4.2

>When I do #include <unistd.h> I get error messages for conflicting
>types of functions, like this:

>/usr/local/gnu/lib/g++-include/unistd.h:57:
>  conflicting types for `int  chown (const char *, short int, short int)'
I ran into the same thing on BSDI (but for slightly different calls), and
went around it by adding "#define chown __hide__chown" before the
"#include_next <stdlib.h>", and a corresponding "#undef chown" after.
Be sure to put them around the correct #include_next, there are two in
each file. In some of the libg++ supplied files you'll see the same approach.

Seeing that the distributed files do the same, I am left wondering why
the original is included in the first place. I guess that the #include_next
is to pick up local differences in symbolic constants, etcetera. In that
case, wouldn't it be a good idea to protect all calls defined in the libg++
include files in the same way?
-- 
Bert Driehuis, driehuis@ooc.uva.nl
Morssingel 243, 2312 EX Leiden, The Netherlands.