From owner-freebsd-questions@FreeBSD.ORG Wed May 11 09:25:19 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B24916A4CE for ; Wed, 11 May 2005 09:25:19 +0000 (GMT) Received: from mail.performancedesign.no (dsl-static-124-226.oeke.tiscali.no [213.234.124.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC8EC43D1D for ; Wed, 11 May 2005 09:25:18 +0000 (GMT) (envelope-from idart@performancedesign.no) Received: from [127.0.0.1] (localhost.performancedesign.no [127.0.0.1]) by mail.performancedesign.no (Postfix) with ESMTP id 342A320ACB; Wed, 11 May 2005 11:25:16 +0200 (CEST) Message-ID: <4281CF7B.1040501@performancedesign.no> Date: Wed, 11 May 2005 11:25:15 +0200 From: Idar Tollefsen Organization: Performance Design User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <4281CA42.6010600@performancedesign.no> <20050511091645.GA25843@xor.obsecurity.org> In-Reply-To: <20050511091645.GA25843@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Alexander Soldatov cc: freebsd-questions@freebsd.org Subject: Re: [OBORONA-SPAM] Re: [OBORONA-SPAM] Re: a problem withcompiling kernel X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2005 09:25:19 -0000 Kris Kennaway wrote: >>>-boundary=2 -ffreestanding -Werror ../../../net/if_gif.c >> >>..and -Werror is in effect: >>"-Werror >> Treat warnings as errors; abort compilation after any warning." >> >>As I said, try setting >>NO_WERROR= yes >>in make.conf. > > That's the brainless and probably wrong approach :) More intelligent > is to wonder why he's seeing this warning when no-one else is: see my > previous response. Agreed :) However, I seem to recall having had the exact same problem somewhere in the gif code on a 4.x version (some time ago), where simply disabling -Werror was the solution. And yes, I did have INET support in there ;) - IT