From owner-freebsd-questions@FreeBSD.ORG Mon Apr 19 17:44:52 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A87951065728 for ; Mon, 19 Apr 2010 17:44:52 +0000 (UTC) (envelope-from joe@netmusician.org) Received: from mail.netmusician.org (dorian.netmusician.org [66.244.95.101]) by mx1.freebsd.org (Postfix) with ESMTP id 345A88FC27 for ; Mon, 19 Apr 2010 17:44:52 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by mail.netmusician.org (Postfix) with ESMTP id 6596FB931; Mon, 19 Apr 2010 13:44:51 -0400 (EDT) X-Virus-Scanned: amavisd-new at netmusician.org Received: from mail.netmusician.org ([127.0.0.1]) by localhost (dorian.netmusician.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id RfYyH1ak8TwR; Mon, 19 Apr 2010 13:44:51 -0400 (EDT) Received: from Shakti.local (c-67-176-145-181.hsd1.in.comcast.net [67.176.145.181]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.netmusician.org (Postfix) with ESMTPSA id 550DDB925; Mon, 19 Apr 2010 13:44:49 -0400 (EDT) Message-ID: <4BCC968C.4000003@netmusician.org> Date: Mon, 19 Apr 2010 13:44:44 -0400 From: Joe Auty User-Agent: Postbox 1.1.4 (Macintosh/20100408) MIME-Version: 1.0 To: glarkin@FreeBSD.org References: <4BCC8E8C.80406@netmusician.org> <4BCC9364.2000404@FreeBSD.org> In-Reply-To: <4BCC9364.2000404@FreeBSD.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Questions about port revision numbers, portsnap, csup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2010 17:44:52 -0000 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!