Re: Re: ext/sysvmsg
| From: | Sascha Schumann | Date: | Tue, 08 Oct 2002 16:18:21 +0000 |
| Subject: | Re: Re: ext/sysvmsg | ||
| References: | 1 | Groups: | php.dev php.qa |
| Request: | Send a blank email to php-dev+get-89231@lists.php.net to get a copy of this message | ||
On Tue, 8 Oct 2002, Melvyn Sopacua wrote:
> Wez,
>
> there's something going wrong with the autoconf logic config.m4 section I
> sent a while back.
> I'll look into it.
As with SysV shared memory, the extension should define its
own structure, if struct msgbuf is not found on the system.
FreeBSD is a good example for an environment which does not
define this structure. glibc only defines it, if all GNU
features have been enabled (-D_GNU_SOURCE).
In that regard, php_sysvmsg.h needs to stop defining
__USE_GNU. An application must not interfere with the C
implementation which the sysvmsg extension is doing here
clearly.
Because __USE_GNU is only a subset of the behavioural changes
which are enabled by _GNU_SOURCE, one can expect that it
might trigger bugs in the C library or lead to other
undesirable results.
- Sascha