At 06:02 9-10-2002, Sascha Schumann wrote:
> > Good point - but also raises, whether to look for this struct in the first
> > place.
> > Why not skip it all, and define it ISO C compliant, in php_ namespace?
>
> That would be a possibility, although you never know how
> engineers at some
> Good point - but also raises, whether to look for this struct in the first
> place.
> Why not skip it all, and define it ISO C compliant, in php_ namespace?
That would be a possibility, although you never know how
engineers at some random company interpreted the standard text
(if th
At 21:11 8-10-2002, Sascha Schumann wrote:
> > 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?
Yes - it s
> 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.
Wez,
there's something going wrong with the autoconf logic config.m4 section I
sent a while back.
I'll look into it.
Jan: if you change the following in main/php_config.h, it should work:
/*msgbuf is called mymsg */
/* #undef msgbuf */
to:
=
Hi Jan,
I wrote that code, but I don't have a FreeBSD box to help fix this :-/
--Wez.
On 10/08/02, "Jan Lehnardt" <[EMAIL PROTECTED]> wrote:
> Hi,
> even more errors show up when the previously quoted lines are commented out:
>
> gcc -Iext/sysvmsg/ -I/mnt/data/cvs/php4clean/ext/sysvmsg/ -DPHP_
Hi Jan,
I had this same problem with some of the streams files.
It was (apparently) due to someone doing a "cvs watch on".
Jim fixed this by tweaking the repository.
What's strange is that both the streams files and those sysvmsg
files were created by me, (although my umask is the usual 022)...
Hi,
even more errors show up when the previously quoted lines are commented out:
gcc -Iext/sysvmsg/ -I/mnt/data/cvs/php4clean/ext/sysvmsg/ -DPHP_ATOM_INC
-I/mnt/data/cvs/php4clean/include -I/mnt/data/cvs/php4clean/main
-I/mnt/data/cvs/php4clean -I/mnt/data/cvs/php4clean/Zend -I/usr/local/inclu
12 matches
Mail list logo
