Date: Fri, 03 Jun 2005 20:40:05 -0500 From: eculp@bafirst.com To: Manfred Antar <null@pozo.com> Cc: Thierry Thomas <thierry@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: Strange problem in Current with Pear. Message-ID: <20050603204005.p6bb9d9uv48gkcg8@mail.bafirst.com> In-Reply-To: <6.2.1.2.2.20050603182218.24599030@pozo.com> References: <20050602215041.hjhyzhxkg0o8wgo4@mail.unixmania.com> <20050603185253.GA57765@graf.pompo.net> <20050603143459.k135bzmo004c4kcw@mail.unixmania.com> <42A0B9F1.4070409@php.net> <20050603155953.m8mal0ornk0kco4o@mail.bafirst.com> <20050603212536.GA98967@graf.pompo.net> <20050603192322.x6cts0hi8gcwk8w0@mail.bafirst.com> <6.2.1.2.2.20050603182218.24599030@pozo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Manfred Antar <null@pozo.com>: > At 05:23 PM 6/3/2005, eculp@bafirst.com wrote: >> Quoting Thierry Thomas <thierry@FreeBSD.org>: >> >>> Le Ven 3 jui 05 =E0 22:59:53 +0200, eculp@bafirst.com <eculp@bafirst.c= om> >>> =E9crivait : >>>> Thanks for the suggestion. I removed the link and the problem >>>> persists. I have two other machines that are working fine with the sam= e >>>> cpu, same pear link, no noticable differences that I can find although >>>> there has to be one ;) So I have three that have this problem and two >>>> that don't. Thanks, again. ed >>> >>> Edwin, >>> >>> Could you please create a package (with `pkg_create -b') on a machine >>> without the problem, transfer this package on a machine with the >>> problem, and install this package (with pkg_add). Then we will know if >>> the problem depends on the build conditions or on the runtime >>> environment. >> >> Yes, of course, Thierry. First I'm trying to understand why I am >> now down from 2 of 5 working to 1 of 5 working and without touching >> php, pear or apache. The only thing that I did on the one that no >> longer works was run portupgrade -a , mergemaster and reset the >> machine to run today's kernel. The one left that works has an old >> kernel from May 19 that I am now backing up and will copy to one of >> the machines that doesn't work just for kicks. I can't imagine that >> the kernel is the problem but hope springs erternal, as they say ;) > > It probably is the kernel. > Read /usr/src/UPDATING, there was a change: > > 20050528: > Kernel parsing of extra options on '#!' first lines of shell > scripts has changed. Manfred, you are correct. Now to figure out how to fix it. I read updating and http://people.freebsd.org/~gad/Updating-20050528.txt but either they weren't clear or I need some rest, probably the latter. I did try it quickly with tcsh and /bin/sh, I use ksh but with no results from any of the three. I'll try at it again in the morning. At least after a week I now know what the problem is :) Thanks again to you and Thierry. If someone has a quick and dirty solution, it would be appreciated. ed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050603204005.p6bb9d9uv48gkcg8>