From owner-freebsd-ports Thu Feb 5 10:06:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27790 for freebsd-ports-outgoing; Thu, 5 Feb 1998 10:06:11 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA27785 for ; Thu, 5 Feb 1998 10:06:09 -0800 (PST) (envelope-from handy@sag.space.lockheed.com) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA22081; Thu, 5 Feb 1998 10:06:08 -0800 Date: Thu, 5 Feb 1998 10:06:08 -0800 (PST) From: Brian Handy To: Bill Fenner Cc: freebsd-ports@FreeBSD.ORG Subject: Re: NAS compile woes In-Reply-To: <98Feb5.100220pst.177476@crevenia.parc.xerox.com> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-ports" On Thu, 5 Feb 1998, Bill Fenner wrote: >Isn't this one of those "XFree86 3.2 vs. 3.3" problems? The NAS port >builds just fine as-is on my machine with XFree86 3.2 . > >Can someone who has NAS compile trouble try these patches instead of >Stefan's? *Grumble* in the interim, I've also figured out that the latest Xig server (V4.1) has sprinkled some evil in my X11 tree. The only reason I know this is I've seen "gnumalloc" show up in a couple of compiles where everything has broken, a sure since Xig has been around. AND, since Xig's uninstall script is broken, either I'm restoring from backup tape or rebuilding X from scratch. BAH! Anyway, bottom line is I don't think I'm a good candidate for checking this [yet]. I'll give it a try soon... Brian