From owner-freebsd-current Mon Jan 22 12:47:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from akira.wossname.net (ct389270-a.lafayt1.in.home.com [24.19.33.26]) by hub.freebsd.org (Postfix) with ESMTP id 9E98437B402; Mon, 22 Jan 2001 12:46:51 -0800 (PST) Received: from akira.wossname.net (localhost.wossname.net [127.0.0.1]) by akira.wossname.net (Postfix) with ESMTP id A372B709C; Mon, 22 Jan 2001 15:46:51 -0500 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Robert Watson Cc: current@FreeBSD.org Subject: Re: Building -STABLE on -CURRENT In-reply-to: Your message of "Sat, 13 Jan 2001 00:00:53 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Jan 2001 15:46:51 -0500 From: Benjamin Lewis Message-Id: <20010122204651.A372B709C@akira.wossname.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert, You wrote: > For the last few days (not sure when it started) I've been unable to build > -STABLE on a -CURRENT machine. This has proven a problem for recent > RELENG_3 MFC's of security fixes; I've tried upgrading to the most recent > -CURRENT on the box, making sure /usr/include is updated, et al. I'm > guessing this is /usr/include pollution in the /usr/src build, but won't > speculate too much more as I'm travelling tomorrow. Attached below is the > breakage from buildworld. [...] > > cd /usr/src/share/syscons/scrnmaps; make build-tools > cc -static -O -pipe -I/usr/src/share/syscons/scrnmaps > -DFIL=\"koi8-r2cp866\" > -o koi8-r2cp866.mk /usr/src/share/syscons/scrnmaps/mkscrfil.c > In file included from /usr/src/share/syscons/scrnmaps/mkscrfil.c:28: > /usr/include/machine/console.h:3: #error "this file includes > > which is deprecated, use instead" I've seen the same thing. I hacked up the -stable source to include the correct -current include files to get past this, but that strikes me as extremely non-optimal. I tried hacking up the Makefile in /usr/src/share/syscons/scrnmaps to use a different include path, but don't have the know-how or mojo to get that working. Have you had any replies to this message or further insights? If so, I'd very much appreciate hearing them. Thank you, -Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message