Re: Bug #14012 Updated: a struct has problem for sysvshm

Btw, isn't sufficient to just mail CVS problems to the list and only create a new bug when really nothing happens? Else I think we clutter the bug system only with small temporary bug reports ... - Markus On Sun, Nov 11, 2001 at 02:58:58AM -0000, mfischer@php.net wrote : > ID: 14012 > Updated by: mfischer > Reported By: yasuo_ohgaki@yahoo.com > Old Status: Open > Status: Closed > Bug Type: Compile Failure > Operating System: linux 2.4.4/glibc 2.2.2 > PHP Version: 4.0CVS-2001-11-10 > New Comment: > > Fixed in CVS. > > Previous Comments: > ------------------------------------------------------------------------ > > [2001-11-10 21:03:41] yasuo_ohgaki@yahoo.com > > Just a build problem. I don't know the code, so patch is not attached. > > make[3]: Entering directory `/home/yohgaki/cvs/php/PHP4/ext/sysvshm' > gcc -I. -I/home/yohgaki/cvs/php/PHP4/ext/sysvshm -I/home/yohgaki/cvs/php/PHP4/main > -I/home/yohgaki/cvs/php/PHP4 -I/home/yohgaki/cvs/php/PHP4/Zend -I/usr/local/include > -I/usr/include/freetype2/freetype -I/home/yohgaki/cvs/php/PHP4/ext/xml/expat > -I/home/yohgaki/cvs/php/PHP4/TSRM -g -Wall -c sysvshm.c && touch sysvshm.lo > sysvshm.c: In function `zif_shm_get_var': > sysvshm.c:305: structure has no member named `first' > sysvshm.c:306: warning: passing arg 4 of `php_var_unserialize' from incompatible pointer > type > sysvshm.c:307: warning: passing arg 1 of `var_destroy' from incompatible pointer type > sysvshm.c:311: warning: passing arg 1 of `var_destroy' from incompatible pointer type > make[3]: *** [sysvshm.lo] Error 1 > make[3]: Leaving directory `/home/yohgaki/cvs/php/PHP4/ext/sysvshm' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/home/yohgaki/cvs/php/PHP4/ext/sysvshm' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/yohgaki/cvs/php/PHP4/ext' > make: *** [all-recursive] Error 1 > [yohgaki@dev PHP4]$