From owner-freebsd-questions Thu Mar 9 12:53:27 2000 Delivered-To: freebsd-questions@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 5FB1A37B835; Thu, 9 Mar 2000 12:53:14 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12T9f4-0006Oz-00; Thu, 09 Mar 2000 20:35:58 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12T9f4-000PuE-00; Thu, 09 Mar 2000 20:35:58 +0000 Date: Thu, 9 Mar 2000 20:35:58 +0000 From: Ben Smithurst To: Majid Almassari Cc: questions@FreeBSD.org, markm@FreeBSD.org Subject: Re: Perl5 installation problems from ports Message-ID: <20000309203558.Q62624@strontium.scientia.demon.co.uk> References: <008f01bf89ef$e8082460$42b6ded0@ibroadcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <008f01bf89ef$e8082460$42b6ded0@ibroadcast.net> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Majid Almassari wrote: > I'm having a problem trying to update perl from 5.004_04 to 5.005_03 or the > latest perl on a FreeBSD 2.2.7-RELEASE. I'm using cvsup with an edited > version of ports-supfile in /usr/share/example, this is how my > ports-supfile looks like: What do the bsd.port.* files in /usr/share/mk look like? I'm guessing you still have "real" versions of those, whereas recent versions of FreeBSD have those simply as stubs to the real versions under /usr/ports/Mk. Try updating those four files (you need bsd.port.mk and bsd.port.{pre,post,subdir}.mk) from RELENG_3 or something (use cgiweb if you can't get them any other way, they're all very small). If you've cvsupped ports then /usr/ports/Mk should be up to date, so you don't need to fiddle with those. -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message