From owner-freebsd-current@FreeBSD.ORG Mon Feb 13 20:19:09 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 4B48A1065728 for ; Mon, 13 Feb 2012 20:19:09 +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 053FF8FC0A for ; Mon, 13 Feb 2012 20:19:09 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:4cc6:9949:a9e5:2d4f] (unknown [IPv6:2001:7b8:3a7:0:4cc6:9949:a9e5:2d4f]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id D21AC5C59; Mon, 13 Feb 2012 21:19:07 +0100 (CET) Message-ID: <4F39703B.20204@FreeBSD.org> Date: Mon, 13 Feb 2012 21:19:07 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120202 Thunderbird/11.0 MIME-Version: 1.0 To: Brandon Falk References: AF413792-CD59-416A-B4E5-27D860FFB57F@turbofuzz.com <4F396020.3030205@gamozo.org> In-Reply-To: <4F396020.3030205@gamozo.org> X-Enigmail-Version: 1.4a1pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Does anyone regularly build HEAD with clang? 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: Mon, 13 Feb 2012 20:19:09 -0000 On 2012-02-13 20:10, Brandon Falk wrote: > I was having the exact same issue. The fix? 'CPP=clang-cpp' instead of > 'CPP=clang -E' in your make.conf. Yes, you should indeed use clang-cpp instead of clang -E. Similarly, never use CPP=gcc -E. This is because in "cpp mode", both gcc and clang behave a little differently than with -E: unknown file extensions (such as the .x extension used for RPC) will be treated as C. But when you use -E, any unknown file extension will be considered an object file, and passed to the linker. Normally, this should lead to errors during building of the rpc include files though... I wonder why this does not happen in your case.