From owner-freebsd-questions Wed Mar 27 23:18:12 2002 Delivered-To: freebsd-questions@freebsd.org Received: from clink.schulte.org (clink.schulte.org [209.134.156.193]) by hub.freebsd.org (Postfix) with ESMTP id 56C9537B41A for ; Wed, 27 Mar 2002 23:18:09 -0800 (PST) Received: from tarmap.nospam.schulte.org (tarmap.schulte.org [209.134.156.198]) by clink.schulte.org (Postfix) with ESMTP id 20FF424424; Thu, 28 Mar 2002 01:18:06 -0600 (CST) Message-Id: <5.1.0.14.0.20020328011306.03f27908@pop3s.schulte.org> X-Sender: X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 28 Mar 2002 01:18:02 -0600 To: Stephen Hoover , questions@freebsd.org From: Christopher Schulte Subject: RE: WU-FTP 2.6.2 compile error on 4.5 p2 In-Reply-To: References: <5.1.0.14.0.20020328005001.03f40da8@pop3s.schulte.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 01:05 AM 3/28/2002 -0600, Stephen Hoover wrote: >Sorry - it was straight from distribution source. I didn't spot >2.6.2 in the ports collection, the only one I could find was 2.6.1_10 >on the website. I will look at the port on the CD, and give that a try. >I'll post the results. The wu-ftpd port was just updated to 2.6.2 ~8 days ago. You might want to cvsup your ports tree to make sure you have the latest files. I run a local cvsupd on my lan so all my systems automatically get updated ports (and system source when needed) files Take a look at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html for info on cvsup, then use /usr/share/examples/cvsup/ports-supfile as a supfile to get started with. Have fun! >Thanks! >Stephen Hoover >Dallas, Texas -- Christopher Schulte http://www.schulte.org/ Do not un-munge my @nospam.schulte.org email address. This address is valid. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message