From owner-freebsd-ports Sat Apr 14 6: 3:10 2001 Delivered-To: freebsd-ports@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 819E437B443 for ; Sat, 14 Apr 2001 06:03:07 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 8614 invoked by uid 1000); 14 Apr 2001 12:01:39 -0000 Date: Sat, 14 Apr 2001 15:01:38 +0300 From: Peter Pentchev To: "Hartmann, O." Cc: freebsd-ports@freebsd.org Subject: Re: some ports do not compile! Message-ID: <20010414150138.G5504@ringworld.oblivion.bg> Mail-Followup-To: "Hartmann, O." , freebsd-ports@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ohartman@klima.physik.uni-mainz.de on Sat, Apr 14, 2001 at 01:56:13PM +0200 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Apr 14, 2001 at 01:56:13PM +0200, Hartmann, O. wrote: > Dear Sirs. > > Some ports won't compile. openmotfif, xv for instance do not compile > on our systems, compilation fails with a patch error (can not find the > appropriate file to patch). Our ports base and Mk-files are up to date > due the fact we cvsupdate them weekly (But I did a cvsupdate today to see > whether the problems has gone or not). > > Any suggestions? Have you cvsup'd from a ports tree from a FreeBSD CD, or have you done a clean cvsup? If from a CD, take a look at items 11 and 12 of: http://www.polstra.com/projects/freeware/CVSup/faq.html#caniadopt ..and see if this helps. If this is the case, your best bet would be to remove the entire ports tree and cvsup it from scratch. G'luck, Peter -- I am not the subject of this sentence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message