From owner-freebsd-ports@FreeBSD.ORG Mon Jun 20 23:09:54 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 751D2106564A for ; Mon, 20 Jun 2011 23:09:54 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from unimail.uni-dortmund.de (mx1.HRZ.Uni-Dortmund.DE [129.217.128.51]) by mx1.freebsd.org (Postfix) with ESMTP id 116378FC0A for ; Mon, 20 Jun 2011 23:09:53 +0000 (UTC) Received: from apollo.emma.line.org (g225199084.adsl.alicedsl.de [92.225.199.84]) (authenticated bits=0) by unimail.uni-dortmund.de (8.14.5/8.14.5) with ESMTP id p5KMVNPg020385 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 21 Jun 2011 00:31:23 +0200 (CEST) Message-ID: <4DFFCA3B.4030307@FreeBSD.org> Date: Tue, 21 Jun 2011 00:31:23 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; de-DE; rv:1.9.2.17) Gecko/20110501 Mnenhy/0.8.3 Thunderbird/3.1.10 MIME-Version: 1.0 To: ports-committers@FreeBSD.org, ports@FreeBSD.org References: <201106202202.p5KM2ro0040297@repoman.freebsd.org> In-Reply-To: <201106202202.p5KM2ro0040297@repoman.freebsd.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: gcc-clang issue (was: cvs commit: ports/sysutils/e2fsprogs Makefile) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jun 2011 23:09:54 -0000 I'v commited this half an hour ago: > mandree 2011-06-20 22:02:53 UTC > > FreeBSD ports repository > > Modified files: > sysutils/e2fsprogs Makefile > Log: > [1] USE_GCC=4.2+, to avoid clang. Port needs -lgcc and -lgcc_s explicitly. > [...] [1] is actually (a) a quick excuse and (b) based on the assumption that USE_GCC will override a clang default ports compiler. I HAVE tried clang, and got a particular kind of linker errors, namely that unrelated .o files redefine the same unrelated symbols - and a crc32.o file redefining libext2fs symbols is curious, to put it mildly. I currently suspect that there are "inline" handling differences between clang and gcc, combined with definitions ("implementations") in .h files, and possibly either different linker behaviour with clang, or actually different symbols. Has anyone seen similar issues (duplicate symbol errors) after switching to clang? Haven't had time to check things in detail, and thought I'd commit USE_GCC right away to unwedge the build for future -exp runs. -- Matthias Andree ports committer