> It's not a typedef but the struct itself that's provided, so that doesn't work.
I'm curious. The following code works here.
struct foo { int a; };
typedef struct foo php_sysmsg;
What did not work for you?
Just using "struct php_sysmsg" is fine, too.
> It boils down to:
At 18:56 10/8/2002 +0200, Sascha Schumann wrote:
>Thus the rule should be: If autoconf finds the definition, we
> use it, otherwise we rely on our own, namespace-protected
> version. Example:
>
> #ifdef HAVE_STRUCT_SYSMSG
> typedef struct sysmsg php_sysmsg;
> #else
>
>
> The struct msgbuf as defined, for example here:
> http://ou800doc.caldera.com/cgi-bin/man/man?msgop+2
>
> defines mtext member as mtext[] while FreeBSD defines it as mtext[1].
Yes, mtext[] is not a valid ISO C construct.
The structures of the SysV IPC interfaces are generally not
d
Hi Sasha,
At 18:18 10/8/2002 +0200, Sascha Schumann wrote:
>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 shoul
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.
