Date: Mon, 19 Apr 2010 14:18:13 -0400 From: Greg Larkin <glarkin@FreeBSD.org> To: Joe Auty <joe@netmusician.org> Cc: freebsd-questions@freebsd.org Subject: Re: Questions about port revision numbers, portsnap, csup Message-ID: <4BCC9E65.20904@FreeBSD.org> In-Reply-To: <4BCC968C.4000003@netmusician.org> References: <4BCC8E8C.80406@netmusician.org> <4BCC9364.2000404@FreeBSD.org> <4BCC968C.4000003@netmusician.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Joe Auty wrote: > Greg Larkin wrote: >> Does pecl-APC not compile, or is it functionally broken after compiling >> succesfully? > It compiles, but once loaded it causes either Apache child processes to > segfault or abort traps depending on where the extension is listed in my > extensions.ini file. Apache itself is running fine, I don't have these > problems on non-PHP pages. Commenting out the apc.so in extensions.ini > makes Apache work again. I haven't done an extensive job of looking for > PHP extension conflicts just yet, but I've slowly been testing my PHP > extensions one by one on a test machine. I got as far as this: > >> extension=session.so >> extension=mysql.so >> extension=json.so >> extension=curl.so >> extension=openssl.so >> ;extension=apc.so > > apc.so is commented out because this was the point where I realized that > it was the culprit after this upgrade. So, I'd imagine that APC has some > sort of problem with PHP 5.3, or possibly one of these extensions? > >>> 2) Is there a way to look at the commit history of the ports I have >>> installed in /usr/ports so that I can verify whether or not I have the >>> revision with this particular fix? Thus far I've been relying on >>> freshports.org and trusting that doing a portsnap will always fetch the >>> latest stuff visible on freshports.org, but now I'm not so sure... >> Is /usr/ports/www/pecl-APC/files/patch-php_apc.c present on your >> machine? If so, then you have the latest commit. >> > Yeah, I have that file... I didn't know that the patch fixed compiling > problems, that was never my problem. > > Perhaps PHP 5.3 needs different APC related php.ini options or > something? I'm generally pretty lazy about doing a diff between the > stock config files and my own... > > I've been trying to no avail to get a good backtrace of my problem, > would that be useful to anybody? Should I keep at this? > > > Thanks for your help Greg! Hi Joe, I believe this is a compatibility problem with the 3.0.x version of the APC extension and PHP 5.3.2. I committed the compiler fix to CVS on 4/12 to get APC building again. I did this at the request of portmgr after the PHP 5.3.2 upgrade, but I didn't go far enough testing the changes. There is a beta version of APC available (3.1.3p1) that is PHP 5.3.2-compatible, and I have prepared a diff for you to try. Can you apply this file to your ports tree and rebuild like so: cd /usr/ports fetch http://people.freebsd.org/~glarkin/diffs/pecl-APC-3.1.3p1.diff patch < pecl-APC-3.1.3p1.diff mkdir /usr/ports/devel/pecl-APC/files/save-patches mv /usr/ports/devel/pecl-APC/files/patch-* \ /usr/ports/devel/pecl-APC/files/save-patches cd devel/pecl-APC make deinstall make clean make install Let me know how that goes, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLzJ5k0sRouByUApARAihmAKCvwVT6DVUR7kNpI/HDc/rfJm197wCfYnYT FRNXpElWFPeLdsDrc9CAA5M= =/0Yu -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BCC9E65.20904>