Subject: Re: /usr/include/zconf.h uses HAVE_UNISTD_H
To: Ignatios Souvatzis <firstname.lastname@example.org>
From: None <email@example.com>
Date: 10/13/1999 18:17:02
>> /usr/include/zconf.h always use HAVE_UNISTD_H, and it would affect
>> definition of z_off_t (defined to off_t when HAVE_UNISTD_H is defined,
>> long when not defined). Is it safe? I believe not every program
>> defines HAVE_UNISTD_H.
>Uhm... as far as I understand (and I only had one cup of coffee this morning):
>Our OS offset type _is_ off_t, and our OS provides a unistd.h that
>defines or uses it. "long" is wrong (well, it would happen to work on
>our LP64 machines, for the time being). So, as long as libz and friends
>use z_off_t where our system calls use offsets, using off_t is
Yes, the above was in my mind.
Isn't it better to change #ifdef HAVE_UNISTD_H in zconf.h into #if 1,
or something similar, so that there will be no mistake?
I checked src/lib/libz/Makefile and it has no HAVE_UNISTD_H...