Re: Change pid_t base type

Hello,

sorry for the late reply, I forgot to hit the reply-all on my last mail
it seems ...
I wasn't aware of this limitation. We are working on 32 bit platforms as
well as 64 bits, so no easy way out.
I suppose we could support two compilation environments by deactivating
fork / kill / getpid if pid_t when long is 32bits.
Do you think it is possible anyway to change the library to enable
overwriting the type pid_t ?
Thanks !

Henri Chataing

On 01/08/18 16:33, Eric Blake wrote:
> On 08/01/2018 09:22 AM, Joel Sherrill wrote:
>> http://pubs.opengroup.org/onlinepubs/009696699/basedefs/sys/types.h.html
>>
>> Says pid_t can be no larger than long if I am reading that correctly.
>
> "The implementation shall support one or more programming environments
> in which the widths of blksize_t, pid_t, size_t, ssize_t, suseconds_t,
> and useconds_t are no greater than the width of type long. The names
> of these programming environments can be obtained using the confstr()
> function or the getconf utility."
>
>>
>> Is POSIX a concern? Or is long 64-bits on all your targets?
>
> If long is 32 bits, do you support two separate compilation
> environments (one for POSIX with 32-bit pid_t, the other for full
> 64-bit pid_t)?
>