From owner-freebsd-current@FreeBSD.ORG Wed Jun 6 16:58:38 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F18C0106564A for ; Wed, 6 Jun 2012 16:58:38 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id AC8048FC14 for ; Wed, 6 Jun 2012 16:58:38 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:300d:9ef5:7e6f:e2bd] (unknown [IPv6:2001:7b8:3a7:0:300d:9ef5:7e6f:e2bd]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id DC8E45C37; Wed, 6 Jun 2012 18:58:37 +0200 (CEST) Message-ID: <4FCF8C3E.6090706@FreeBSD.org> Date: Wed, 06 Jun 2012 18:58:38 +0200 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120529 Thunderbird/13.0 MIME-Version: 1.0 To: Sevan / Venture37 References: <4FCE8306.1020000@gmail.com> <4FCF35BF.5080006@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.5a1pre Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" Subject: Re: Unable to buildworld with ccache 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, 06 Jun 2012 16:58:39 -0000 On 2012-06-06 18:51, Sevan / Venture37 wrote: > Worked a treat, now it barfs on libelf ... > /usr/src/lib/libelf/elf_scn.c:198:41: error: equality comparison with > extraneous parentheses [-Werror,-Wparentheses-equality] > if (((&e->e_u.e_elf.e_scn)->stqh_first == ((void *)0))) { > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~ > /usr/src/lib/libelf/elf_scn.c:198:41: note: remove extraneous > parentheses around the comparison to silence this warning This is a lot harder to fix, and has limited usefulness, so I suggest you build with NO_WERROR for now.