Ok, now I have no idea. I'd suggest grabbing the latest RC or waiting
for the release at this point. CVS versions require a bunch of tools to
generate files (autoconf, libtool, etc.). The RC and releases come with
the generated files. There appears to be some odd problem with you
build environment. What it is, I don't know.
Pablo Sabatino wrote:
>
> I deleted php4 and downladed the software again from the cvs and compiled
> it.
> This is the error message when executed ./make
>
> gmake: *** [zend_language_parser.c] Violación de segmento
> pablo@pablito:~/php4/Zend > cd ..
> pablo@pablito:~/php4 > gmake
> Making all in Zend
> gmake[1]: Entering directory `/home/pablo/php4/Zend'
> bison -y -p zend -v -d ./zend_language_parser.y -o zend_language_parser.c
> gmake[1]: *** [zend_language_parser.c] Violación de segmento
> gmake[1]: Leaving directory `/home/pablo/php4/Zend'
> gmake: *** [all-recursive] Error 1
> pablo@pablito:~/php4 >
>
> The version bison is: 1.28 and this messages is from ./configure [args]
> The system operating is SUSE 6.4.
>
> Configuring Zend
> checking bison version... 1.28 (ok)
> checking for limits.h... (cached) yes
> checking for malloc.h... yes
> checking for string.h... (cached) yes
> checking for unistd.h... (cached) yes
> checking for stdarg.h... (cached) yes
> checking for sys/types.h... (cached) yes
> checking for signal.h... (cached) yes
> checking for unix.h... (cached) no
> checking for dlfcn.h... yes
> checking for size_t... (cached) yes
> checking return type of signal handlers... void
> checking for dlopen in -ldl... (cached) yes
> checking for dlopen... (cached) yes
> checking for uint... yes
> checking for ulong... yes
> checking for vprintf... (cached) yes
> checking for 8-bit clean memcmp... yes
> checking for working alloca.h... (cached) yes
> checking for alloca... (cached) yes
> checking for memcpy... (cached) yes
> checking for strdup... (cached) yes
> checking for getpid... yes
> checking for kill... yes
> checking for strtod... yes
> checking for strtol... yes
> checking for finite... yes
> checking for fpclass... no
> checking whether sprintf is broken... (cached) no
> checking for finite... (cached) yes
> checking for isfinite... no
> checking for isinf... yes
> checking for isnan... yes
> checking whether fp_except is defined... no
> checking whether to enable experimental ZTS... no
> checking whether to enable inline optimization for GCC... no
> checking whether to enable a memory limit... no
> checking whether to enable Zend debugging... no
> checking for inline... inline
>
> what the matter???
> Could resolve it?
>
> Please, help me!
>
> Thanks pablo!
>
> > From: "Kelly Cochran" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, April 19, 2001 6:41 PM
> > Subject: Re: [PHP] `AM_PROG_LIBTOOL' not found in library
> >
> >
> > You'll likely have to do a make distclean in the root PHP dir as well.
> > Without that, make is probably finding the zend_ini_parser.c that your
> > old bison created from zend_ini_parser.y, and therefore doesn't
> > regenerate it. Or you could probably also simply 'touch
> > Zend/zend_ini_parser.y' and that should also cause make to regen the .c
> > file. Either that, or you could simply nuke the whole dir, and checkout
> > from CVS again doing the './buildconf; ./configure <args>; make' cycle
> > again.
-- -
Kelly Cochran <[EMAIL PROTECTED]>
Technical Staff - funschool.com Corporation
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
