From owner-freebsd-ports Fri Feb 12 22:41:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03998 for freebsd-ports-outgoing; Fri, 12 Feb 1999 22:41:48 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from pobox.com (lakertya-1-18.mdm.mkt.execpc.com [169.207.118.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03990 for ; Fri, 12 Feb 1999 22:41:41 -0800 (PST) (envelope-from hamilton@pobox.com) Received: from pobox.com (localhost [127.0.0.1]) by pobox.com (Postfix) with ESMTP id 786E645910; Sat, 13 Feb 1999 00:41:35 -0600 (CST) To: Brian Handy Cc: ports@FreeBSD.ORG Subject: Re: mgv configure woes In-reply-to: Your message of "Fri, 12 Feb 1999 22:54:43 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Feb 1999 00:41:35 -0600 From: Jon Hamilton Message-Id: <19990213064135.786E645910@pobox.com> Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , Brian Handy wrote: } Hi folks, } } Satoshi's ports-build-tester claims mgv is broken, and the error on the } build page is "configure error". I'm running 2.2, and I don't have any } 3.x machines here just now...but I speculate that's where the problem is. } Could somebody who's running 3.x/4.x give it a try and maybe see what's } up? Using $Id: Makefile,v 1.13 1998/12/03 12:26:40 vanilla Exp $ and assuming it's still the most current, I just built it without incident or complaint on a 3.0-STABLE system built from sources a couple of weeks old; if there is a problem, it must be with -current. Note that I didn't actually test it other than to fire it up and poke at the initial screen a bit, so it is possible that something useful is misconfigured. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message