From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 13:54:51 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C46B1065673 for ; Sun, 3 Oct 2010 13:54:51 +0000 (UTC) (envelope-from rpaulo@freebsd.org) Received: from karen.lavabit.com (karen.lavabit.com [72.249.41.33]) by mx1.freebsd.org (Postfix) with ESMTP id E1FB58FC1B for ; Sun, 3 Oct 2010 13:54:50 +0000 (UTC) Received: from d.earth.lavabit.com (d.earth.lavabit.com [192.168.111.13]) by karen.lavabit.com (Postfix) with ESMTP id 1889311B821; Sun, 3 Oct 2010 08:54:50 -0500 (CDT) Received: from 10.0.10.3 (221.163.108.93.rev.vodafone.pt [93.108.163.221]) by lavabit.com with ESMTP id 74QDDOX8SNMC; Sun, 03 Oct 2010 08:54:50 -0500 Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Rui Paulo In-Reply-To: <20101003134111.GA98699@oriental.arm.org> Date: Sun, 3 Oct 2010 14:54:45 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <9825922F-0808-4A60-97B7-2A6818FA409F@FreeBSD.org> References: <20101003134111.GA98699@oriental.arm.org> To: dlt@mebtel.net X-Mailer: Apple Mail (2.1081) Cc: current@FreeBSD.org Subject: Re: Another clang problem 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: Sun, 03 Oct 2010 13:54:51 -0000 On 3 Oct 2010, at 14:41, Derek Tattersall wrote: > In updating gnash to 8.8 the build failed while linking with = libvgl.so. My > current system was built last week, with both kernel and world built > with clang. The linkage failure was due to an inlined function, > "set4pixels" which is only referred to, as far as I can tell, within = the > source file simple.c which contains the function definition. >=20 > I rebuilt libvgl.so using gcc and gnash linked properly. It seems, at > least in this case, that clang has some problems dealing with inlined > functions. We are still in the process of identifying which ports have problems, = but we are aware that building ports with clang is not an easy job: = several ports assume a gcc behavior and there some LLVM/Clang problems = that need to be ironed out. Given this, we need some sort of way to identify ports that can be built = with clang, but that requires man-hours. Regards, -- Rui Paulo