From owner-freebsd-current@FreeBSD.ORG Tue Jun 28 19:17:35 2011 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 417C4106566B for ; Tue, 28 Jun 2011 19:17:35 +0000 (UTC) (envelope-from eric@shadowsun.net) Received: from mail.atlantawebhost.com (dns1.atlantawebhost.com [66.223.40.39]) by mx1.freebsd.org (Postfix) with ESMTP id E95FC8FC15 for ; Tue, 28 Jun 2011 19:17:34 +0000 (UTC) Received: (qmail 18551 invoked from network); 28 Jun 2011 15:10:53 -0400 Received: from yktgi01e0-s5.watson.ibm.com (HELO atom-edge.watson.ibm.com) (129.34.20.19) by mail.atlantawebhost.com with SMTP; 28 Jun 2011 15:10:53 -0400 Message-ID: <4E0A273C.2010303@shadowsun.net> Date: Tue, 28 Jun 2011 15:10:52 -0400 From: Eric McCorkle User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4E07EBA2.70500@shadowsun.net> <4E08778D.2050302@FreeBSD.org> <4E08A8DB.2020805@shadowsun.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Clang buildworld failure due to multiple definitions of __isnanf 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: Tue, 28 Jun 2011 19:17:35 -0000 On 6/28/11 1:42 AM, Benjamin Kaduk wrote: > On Tue, 28 Jun 2011, Benjamin Kaduk wrote: > >> On Mon, 27 Jun 2011, Eric McCorkle wrote: >> >>> make.conf: >>> CPUTYPE?=core2 >>> .if !defined(CC) || ${CC} == "cc" >>> CC=clang >>> CFLAGS=-Qunused-arguments >>> .endif >>> .if !defined(CXX) || ${CXX} == "c++" >>> CXX=clang++ >>> .endif >>> NO_WERROR= >>> WERROR= >>> NO_FSCHG= >>> PERL_VERSION=5.12.3 >>> >>> Just noticed, the CFLAGS would disable optimization, which would >>> explain why no one else seems to see this. Still, I think the >>> underlying issue warrants investigation. >> >> I seem to recall that our gcc-4.2 with -O0 is known to be buggy -- >> certainly I just tripped over a panic in a third-party kernel module >> build using bsd.kmod.mk with -O0 that was fixed by compiling the >> object in question with -O. >> It is not terribly easy to search for, but my archives find at least >> http://lists.freebsd.org/pipermail/freebsd-current/2007-August/076028.html >> >> >> I would try with -O1 and confirm that your issues go away, and not >> spend time on the core issue if it proves to be a gcc bug. >> >> Unfortunately, we are stuck with an old gcc in base ... though I have >> yet to see if clang -O0 has issues with my module. > > Wow, I juxtaposed the two compilers due to working on too little sleep. > Please disregard, and sorry for the noise. > Getting rid of the CFLAGS in my make.conf got rid of the multiple definitions (I still think the underlying issue merits investigation and resolution) for both compilers.