[PHP] Clean PHP 5.2.12 Build Core Dumping

2010-01-08 Thread Don O';Neil
I'm trying to build a clean version of php 5.2.12 on my FreeBSD 6.1 box and even with NO OPTIONS, php core dumps during the make test phase. How do I go about tracking down what is causing this problem? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/

[PHP] Clean PHP 5.2.12 Build Core Dumping

2010-01-08 Thread Don O';Neil
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. 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

[PHP] RE: Clean PHP 5.2.12 Build Core Dumping

2010-01-09 Thread Don O';Neil
o:free...@edvax.de] > Sent: Friday, January 08, 2010 10:35 PM > To: Don O'Neil > Cc: php-general@lists.php.net; freebsd-questi...@freebsd.org > Subject: Re: Clean PHP 5.2.12 Build Core Dumping > > On Fri, 8 Jan 2010 16:18:11 -0800, "Don O'Neil" > wrote: &

[PHP] RE: Clean PHP 5.2.12 Build Core Dumping

2010-01-09 Thread Don O';Neil
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

[PHP] RE: Clean PHP 5.2.12 Build Core Dumping

2010-01-10 Thread Don O';Neil
> > I tried adding WITHOUT_X11=yes to /etc/make.conf as well as X11BASE= > and > > X11BASE="", but I still get the same error. > > Remove them. This makes sure they are not defined, not even > empty (as in "#define BLA -> symbol 'BLA' is defined"). > > > Where to go from here? Do I have and old v

RE: [PHP] RE: Clean PHP 5.2.12 Build Core Dumping / Can't Build Port - FreeBSD 6.1

2010-01-11 Thread Don O';Neil
Ok.. just for grins I installed a new instance of 6.1, NO Patches, just straight off the ISO... I loaded the ports that came WITH the distro, and was able to make php 5.1.2 ok... When I did a portsnap fetch, portsnap extract, then went into the /usr/ports/lang/php5 and just typed make I get the s

RE: [PHP] RE: Clean PHP 5.2.12 Build Core Dumping / Can't Build Port - FreeBSD 6.1

2010-01-12 Thread Don O';Neil
; from that file and > > 4.make all-depend-list > 5.make clean all depend soft > 6.make menuconfig set X11 disable > 7.make &&make install > > > 2010/1/12 Don O'Neil : > > Ok.. just for grins I installed a new instance of 6.1, NO Patches, > just > >

RE: [PHP] RE: Clean PHP 5.2.12 Build Core Dumping / Can't Build Port - FreeBSD 6.1

2010-01-13 Thread Don O';Neil
onf > >> 2.remove > >> X11BASE="" > >> from that file and > >> > >> 4.make all-depend-list > >> 5.make clean all depend soft > >> 6.make menuconfig set X11 disable > >> 7.make &&make install >

[PHP] Any known security issues with IMAP?

2007-10-03 Thread Don O';Neil
Are there any known security issues/concerns with compiling PHP with imap/pop3 support? Such as hijacking php pages and relaying spam, etc...? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

[PHP] Any known security issues with IMAP?

2007-10-03 Thread Don O';Neil
Are there any known security issues/concerns with compiling PHP with imap/pop3 support? Such as hijacking php pages and relaying spam, etc...? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

[PHP] Core dumps with --with-openssl

2007-10-04 Thread Don O';Neil
I just tried rebuilding my apache & php to the latest version and now whenever I try to start it it core dumps. If I remove the --with-openssl and build with 4.4.6 of php at least it starts. I can't even get my old version to build now... Is there a work-around for this? The setup is as follows:

[PHP] OpenSSL problem

2007-10-05 Thread Don O';Neil
Any time I compile PHP 4.4.7 with --with-ssl my apache 1.3.39 server core dumps on my FreeBSD 6.1 box. Anyone have a work around for this or suggestions where to look? I was having a similar problem with Curl, but once I told curl where the OpenSSL home dir was that solved that problem. The locati