From owner-freebsd-current@FreeBSD.ORG Wed Nov 21 14:53:21 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4440016A419 for ; Wed, 21 Nov 2007 14:53:21 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [212.192.164.5]) by mx1.freebsd.org (Postfix) with ESMTP id E447713C45B for ; Wed, 21 Nov 2007 14:53:20 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.50) id 1IuqxB-0006bE-BT; Wed, 21 Nov 2007 20:53:25 +0600 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.1/8.14.1) with ESMTP id lALEuqNi082312; Wed, 21 Nov 2007 20:56:52 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.1/8.14.1/Submit) id lALEulj0082241; Wed, 21 Nov 2007 20:56:47 +0600 (NOVT) (envelope-from danfe) Date: Wed, 21 Nov 2007 20:56:46 +0600 From: Alexey Dokuchaev To: Ruslan Ermilov Message-ID: <20071121145646.GA80149@regency.nsu.ru> References: <20071121090527.GA57912@regency.nsu.ru> <20071121135823.GE1617@team.vega.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071121135823.GE1617@team.vega.ru> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Wed, 21 Nov 2007 14:56:55 +0000 Cc: current@freebsd.org Subject: Re: make kernel build error on recent -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2007 14:53:21 -0000 On Wed, Nov 21, 2007 at 04:58:24PM +0300, Ruslan Ermilov wrote: > I cannot reproduce this on neither RELENG_7 or HEAD, compiling > GENERIC or LINT (you didn't tell what combination you're using), Indeed. GENERIC is building just fine. Will investigate further. > but NO_WERROR never affected -Werror in kernel and module builds. Right, I overlooked it. > In this case, you can reset -Werror like this: > > make ... WERROR= I'd still like to figure out what is going wrong with my custom kernel. Thanks! ./danfe