From owner-freebsd-questions@FreeBSD.ORG Fri May 29 20:36:11 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E4251065674 for ; Fri, 29 May 2009 20:36:11 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 5EAB98FC1F for ; Fri, 29 May 2009 20:36:10 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from sarevok.dnr.servegame.org (mailhub.lan.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id 890A57E837; Fri, 29 May 2009 12:36:09 -0800 (AKDT) From: Mel Flynn To: freebsd-questions@freebsd.org Date: Fri, 29 May 2009 22:36:07 +0200 User-Agent: KMail/1.11.3 (FreeBSD/8.0-CURRENT; KDE/4.2.3; i386; ; ) References: <70C0964126D66F458E688618E1CD008A0793EE1C@WADPEXV0.waddell.com> In-Reply-To: <70C0964126D66F458E688618E1CD008A0793EE1C@WADPEXV0.waddell.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905292236.07971.mel.flynn+fbsd.questions@mailing.thruhere.net> Cc: Gary Gatten Subject: Re: sys/sched.h: present but cannot be compiled X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 20:36:11 -0000 On Friday 29 May 2009 22:04:57 Gary Gatten wrote: > On 6.0 RELEASE I keep getting this error. I've read a bunch of links > and tried tweaking some source to no avail. Any help resolving this > would be appreciated. It sounds kinda bad to me, but things are working > *OK*.... I don't like warnings, let alone those that have to do with > scheduling and threads... Tell the GNU autoconf maintainers to fix their macros then. They're trying to include a header with _KERNEL defined outside the kernel. And they should be using anyway. -- Mel