From owner-freebsd-ports@FreeBSD.ORG Wed Jul 4 12:21:28 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FAEF106566C for ; Wed, 4 Jul 2012 12:21:28 +0000 (UTC) (envelope-from scheidell@FreeBSD.org) Received: from mx2.secnap.com.ionspam.net (mx2.secnap.com.ionspam.net [216.134.223.54]) by mx1.freebsd.org (Postfix) with ESMTP id C59E08FC08 for ; Wed, 4 Jul 2012 12:21:27 +0000 (UTC) Received: from mx2.secnap.com.ionspam.net (unknown [10.71.0.54]) by mx2.secnap.com.ionspam.net (Postfix) with ESMTP id 47FF6D23CF2 for ; Wed, 4 Jul 2012 08:21:27 -0400 (EDT) X-Virus-Scanned: SpammerTrap(r) VPS-1500 2.18 at mx2.secnap.com.ionspam.net Received: from USBCTDC001.secnap.com (unknown [10.70.1.1]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx2.secnap.com.ionspam.net (Postfix) with ESMTPS id 64AF6D23C30 for ; Wed, 4 Jul 2012 08:21:26 -0400 (EDT) Received: from USBCTMX001.secnap.com (::ffff:10.70.1.129) by USBCTDC001.secnap.com (::ffff:10.70.1.1) with Microsoft SMTP Server (TLS) id 14.0.722.0; Wed, 4 Jul 2012 08:21:26 -0400 Message-ID: <4FF43544.8060600@FreeBSD.org> Date: Wed, 4 Jul 2012 08:21:24 -0400 From: Michael Scheidell Organization: SECNAP Network Security Corp User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.2.20) Gecko/20110804 Thunderbird/3.1.12 MIME-Version: 1.0 To: References: <20120704080536.37072aba@scorpio> In-Reply-To: <20120704080536.37072aba@scorpio> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: unable to build openjade after updating perl X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2012 12:21:28 -0000 On 7/4/12 8:05 AM, Jerry wrote: > Has anyone else experienced this phenomenon after updating the Perl > port? > yes, for years and years. if you update perl, from something that is working to the new version, you will always see issues with random ports not building, or not needed (p5-(something) is already in perl. did you follow /usr/ports/UPDATING? EXACTLY? The following is never recommended, not by perl@, not by the joint chiefs, nobel comittee, on the iron chief: (but I do it here every time, because I can't get an upgrade to work without it) AFTER doing everyting in /usr/ports/UPDATING, see what is left in the old perl dirs cd /usr/local/lib/perl5 ls cd /usr/local/lib/perl5/ scanner2.hackertrap.net# ls 5.12.4 5.16.0 site_perl (just lists what was NOT updated, copied over to, installed into new perl) rsync -avun 5.12.4 5.16.0 cd site_perl repeat. Now, here is the part you don't want to do: take out the -n (dry run), because if you do, you might actually copy over something that was missing, and might make your ports work again. (or break them worse) but, then again, openjade might just not be compatible with perl5.16, which is also a possibility, and you won't get anywhere until it is upgraded. actually, what do we do in practice for our commercial systems? leave well enough alone. it took at least a year going from 5.10 to 5.12 before all the bugs in the p5-* ports were worked out. When we do upgrade, we wipe everything out and start all over: pkg_delete -A portmaster private/metaport install everything back from our private binary package builds. if we don't, then 'strange' things always happen. We do this for perl and php. ymmv. -- Michael Scheidell, CTO >*| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell