From owner-freebsd-ports@FreeBSD.ORG Thu Mar 17 18:38:11 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D63B816A4CE; Thu, 17 Mar 2005 18:38:11 +0000 (GMT) Received: from forrie.com (forrie.ne.client2.attbi.com [24.147.45.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF7BA43D39; Thu, 17 Mar 2005 18:38:10 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from [192.168.1.99] (i-99.forrie.net. [192.168.1.99]) (authenticated bits=0) by forrie.com with ESMTP id j2HIc5Tr018035; Thu, 17 Mar 2005 13:38:06 -0500 (EST) (envelope-from forrie@forrie.com) Message-ID: <4239CE8D.6000104@forrie.com> Date: Thu, 17 Mar 2005 13:38:05 -0500 From: Forrest Aldrich User-Agent: Mozilla Thunderbird 1.0.1 (Windows/20050307) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kent Stewart References: <42392B72.1060301@forrie.com> <4239779D.3020903@mac.com> <4239C3E5.7070409@forrie.com> <200503171032.35297.kstewart@owt.com> In-Reply-To: <200503171032.35297.kstewart@owt.com> X-Enigmail-Version: 0.90.1.1 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com) X-MailScanner-LocalNet: Found to be clean cc: ports@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: Packages and dependencies... X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Mar 2005 18:38:12 -0000 This is a brand new system that was installed and CVSup'd yesterday (late EST), and so there really aren't any ports installed yet. When I went to build amavisd-new via "make package-recursive" this problem occured. So is it that the port itself isn't up-to-date (the one generating the error), or? I will keep reading the UPDATING file, but I am not sure how that applies here to a new system with nothing installed. I found this: 20050201: AFFECTS: users of lang/perl5 and lang/perl5.8 AUTHOR: tobez@FreeBSD.org lang/perl5 has been updated to 5.6.2, and lang/perl5.8 has been updated to 5.8.6. you should update everything depending on perl, that is: * first, upgrade your perl installation (use either lang/perl5 or lang/perl5.8, the latter being recommended); * for FreeBSD 4.X, run "use.perl port", so that the system knows you have 5.8.6 or 5.6.2; this step is not needed on FreeBSD 5.X and FreeBSD -CURRENT; * run some magic incantations to upgrade all ports depending on perl, that is run something like : portupgrade -f `(pkg_info -R perl-5\* |tail +4; \ find /usr/local/lib/perl5/site_perl/5.[68].[1245] -type f -print0 \ | xargs -0 pkg_which -fv | sed -e '/: ?/d' -e 's/.*: //')|sort -u` This is likely to fail for a few ports, you'll have to upgrade them afterwards by hand. Thanks, Forrest Kent Stewart wrote: >On Thursday 17 March 2005 09:52 am, Forrest Aldrich wrote: > > >>I am trying a different angle: build the port as-is in the ports >>directory, with the expectation to use "pkg_add -p" to alter the >>installation PATH. >> >>However, one of the dependencies relies upon an older version of perl >>that isn't being built: >> >>===> Configuring for p5-Unix-Syslog-0.100 >>env: /usr/local/bin/perl5.8.5: No such file or directory >>*** Error code 127 >> >>Instead, I have perl5.8.6 in there. >> >>There must be a way to correct this dependency skew.? >> >> > >You didn't read /usr/ports/UPDATING. There is a sequence that you have >to follow when you update perl. When follow the instructions in >UPDATING and you rebuild the ports such as p5-\*, you won't see your >problem. > >Kent > > > >>Thanks. >> >>_______________________________________________ >>freebsd-ports@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-ports >>To unsubscribe, send any mail to >>"freebsd-ports-unsubscribe@freebsd.org" >> >> > > >