php-general Digest 10 Jan 2010 14:39:56 -0000 Issue 6531
Topics (messages 300939 through 300940):
Re: Clean PHP 5.2.12 Build Core Dumping
300939 by: Don O'Neil
300940 by: Michael A. Peters
Administrivia:
To subscribe to the digest, e-mail:
[email protected]
To unsubscribe from the digest, e-mail:
[email protected]
To post to the list, e-mail:
[email protected]
----------------------------------------------------------------------
--- Begin Message ---
Well, I hadn't edited the Makefiles, I was planning on it (but won't now
that you pointed out the make option), but never got past making the generic
port....
I tried adding WITHOUT_X11=yes to /etc/make.conf as well as X11BASE= and
X11BASE="", but I still get the same error.
Where to go from here? Do I have and old version of something that is
causing this? I get this error _right away_ before anything is even built.
Thanks!
> If installing with the ports system you shouldn't need to be editing
> any
> Makefiles. make config will give you list of options you may select
> from.
> Note there is an initial build/install of PHP itself and a second port
> called php5-extensions which you then install for all the modules.
> Again, a
> make config will list all options. No need to mess with Makefiles.
>
> > X11BASE is now deprecated. Unset X11BASE in make.conf and try again.
> > *** Error code 1
> >
>
> Try putting WITHOUT_X11=yes into /etc/make.conf. Some PHP modules such
> as GD
> try and pull in X dependencies; this will short circuit that.
--- End Message ---
--- Begin Message ---
Don O'Neil wrote:
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
I've experienced the same type of issue when building php RPM's on Linux.
The solution is to either remove the previous php build or build it in a
chroot build environment (such as mock for RPM based distros).
--- End Message ---
