From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 14:04:28 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 70A1C1065673 for ; Sun, 3 Oct 2010 14:04:28 +0000 (UTC) (envelope-from dlt@mebtel.net) Received: from mail962c35.nsolutionszone.com (mail962c35.nsolutionszone.com [209.235.152.152]) by mx1.freebsd.org (Postfix) with ESMTP id 141C38FC17 for ; Sun, 3 Oct 2010 14:04:27 +0000 (UTC) X-POP-User: dlt.mebtel.net Received: from localhost (99-194-23-158.dyn.centurytel.net [99.194.23.158]) by mail962c35.nsolutionszone.com (8.13.6/8.13.1) with ESMTP id o93E4PLm005639; Sun, 3 Oct 2010 14:04:26 GMT Date: Sun, 3 Oct 2010 10:04:25 -0400 From: Derek Tattersall To: Rui Paulo Message-ID: <20101003140425.GA98803@oriental.arm.org> References: <20101003134111.GA98699@oriental.arm.org> <9825922F-0808-4A60-97B7-2A6818FA409F@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9825922F-0808-4A60-97B7-2A6818FA409F@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-CSC: 0 X-CHA: v=1.1 cv=uVrN/md/HB0tP65KUyQDxMIwb8qE6v9oaXSvIWlxpDE= c=1 sm=1 a=GPr01A5e9VcA:10 a=kj9zAlcOel0A:10 a=5FSmvsqyZ8dLHOg+TByL6Q==:17 a=6I5d2MoRAAAA:8 a=xwPayol1AAAA:8 a=CjxXgO3LAAAA:8 a=pGLkceISAAAA:8 a=qLhAwP0VI7mI3CG8kv0A:9 a=2z0-z6XcfZcqZkgloxIA:7 a=er4h19l_Ptjy-15PX5RXyvOg2YEA:4 a=CjuIK1q_8ugA:10 a=SV7veod9ZcQA:10 a=0Ob1RWNGeVAA:10 a=rC2wZJ5BpNYA:10 a=MSl-tDqOz04A:10 a=5FSmvsqyZ8dLHOg+TByL6Q==:117 Cc: current@freebsd.org Subject: Re: Another clang problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dlt@mebtel.net 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 14:04:28 -0000 * Rui Paulo [101003 09:57]: > 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. > > > > 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 I was not completely clear, I'm afraid. Gnash was built with gcc under all circumstances. libvgl.so is part of the world build and is installed in /usr/lib. It was originally built with clang when I built both the kernel and the world with clang last week. I found that building /usr/src/lib/libvgl with gcc was necessary to get gnash to build properly. -- Best regards, Derek Tattersall dlt@mebtel.net dlt666@yahoo.com dtatters@gmail.com