From owner-freebsd-current@FreeBSD.ORG Mon Jun 6 21:17:11 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDCAC16A41C for ; Mon, 6 Jun 2005 21:17:11 +0000 (GMT) (envelope-from lord.freebsdlists@gmail.com) Received: from ecf.puc.edu (ecf2.puc.edu [12.16.216.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 021A843D49 for ; Mon, 6 Jun 2005 21:17:10 +0000 (GMT) (envelope-from lord.freebsdlists@gmail.com) Received: from gate1.puc.edu (gate1.puc.edu [192.168.230.3]) by ecf.puc.edu (8.11.6/8.10.1) with ESMTP id j56LH9P14642 for ; Mon, 6 Jun 2005 14:17:09 -0700 (PDT) Received: from [10.201.136.242] ([10.201.136.242]) by gate1 with IMSS; Mon, 06 Jun 2005 14:15:57 -0700 Message-ID: <42A4BD7E.7050506@gmail.com> Date: Mon, 06 Jun 2005 14:17:50 -0700 From: Jeff Hubbard User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <200506041101.j54B1ptL025154@grovel.grondar.org> <20050604065709.eyc2anr5co4w08sk@mail.bafirst.com> <20050604122523.GB57893@over-yonder.net> <20050604075923.ip4rqz6dwko40o8s@mail.bafirst.com> <42A1D1D9.7030204@gmail.com> <20050604154218.qwcz4j2dwo0w8k8g@mail.bafirst.com> In-Reply-To: <20050604154218.qwcz4j2dwo0w8k8g@mail.bafirst.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: pear broken on current. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 21:17:12 -0000 Hi folks, So I took a look at /usr/local/bin/pear, and I found nothing amiss. I tried executing 'pear config-show' and besides an error message for zend_hash.c(which is probably the result of my recent port upgrade), I found nothing amiss. My interpreter is the exact same as eculp@bafirst.com's, even. Some things that might be different from eculp@bafirst.com's setup: I'm running the very latest kernel for 5.3-CURRENT. I cvsup'ed it and ports today, and did a portupgrade(thus the error with zend_hash.c). The one thing noted about the kernel handling interpreters differently appears to have no effect on this particular problem, at least that I can note. Perhaps I should cvsup 5.4 and test on there as well? Jeff