No, someone forgot to touch the generated parse.c when
he/she updated parse.y. (parse.c needs to be always committed
separately AND after committing parse.y)
--Jani
On Sun, 18 Jan 2004, Timm Friebe wrote:
>[EMAIL PROTECTED]:~/devel/php/php > make
>no /usr/home/thekid/devel/php/php/ext/sqlite/libsqlite/src/parse.y
>no:No such file or directory
>*** Error code 1
>
>[EMAIL PROTECTED]:~/devel/php/php > grep 'parse.y' Makefile
>/usr/home/thekid/devel/php/php/ext/sqlite/libsqlite/src/parse.c:
>/usr/home/thekid/devel/php/php/ext/sqlite/libsqlite/src/parse.y
> $(LEMON)
>/usr/home/thekid/devel/php/php/ext/sqlite/libsqlite/src/parse.y
>
>Shouldn't configure bail out with an error messag if it can't find
>$(LEMON)?
>
>- Timm
>
>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
