Clean PHP 5.2.12 Build Core Dumping

[Polytropon]

On Fri, 8 Jan 2010 16:18:11 -0800, "Don O'Neil" <lists at lizardhill.com> wrote:
> Ok... more info on the problem...
> 
> I started with a clean untarred archive, ad just ran ./configure, make, make
> test.... I get a core dump.

Maybe this is not a FreeBSD source?

I'd suggest using the FreeBSD ports system for installation from
source (i. e. tar archives). PHP 5.2.12 seems to be availabe.
You can use

	# cd /usr/ports/lang/php5
	# make
	# make install

Make sure - not "make sure" :-) - that your ports tree is up to
date in order to recieve the latest version.



> After running gdb on the core dump I noticed it was the sqlite stuff that
> was dumping, so I re-ran configure with --without-sqlite
> --without-pdo-sqlite --with-mysql=/usr/local/mysql

Check the available options that can be set for the php5 port
at compile time, either via "make config", or enter them
manually (e. g. in Makefile.local - I'm not sure if this
mechanism is still supported).



> Now the gdb shows this:
> 
> Core was generated by `php'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x081d50a7 in sqlite3Select (pParse=0xbbc00080, p=0x0, eDest=164102200,
>     iParm=0, pParent=0x24, parentTab=139141440, pParentAgg=0x84c10d8,
> aff=0x0)
>     at
> /usr/local/directadmin/customapache/php-5.2.11/ext/pdo_sqlite/sqlite/src/sel
> ect.c:3172
> 3172          for(j=0; j<pGroupBy->nExpr; j++){
> 
> 
> First off, the compile directory listed is wrong, don't know where it got
> php-5.2.11 from, that's the last version I built and is installed on this
> system. Maybe it's pulling that from the system php? 

Yes, correct.



> Secondly, even though I've told it not to use sqlite, it still seems to be.

It is - by 5.2.11 (or by directadmin). Seems that you've not
installed 5.2.12 with your custom options yet.



> Any help here would be appreciated in moving forward. My whole reason for
> needing to rebuild php is I need the pdo_mysql module instead of the
> pdo_sqlite version.

As I said, I would suggest to try to achieve this through
the ports system. It's easier than fighting ./configure. :-)



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...