Date: Sun, 3 Oct 2010 10:04:25 -0400 From: Derek Tattersall <dlt@mebtel.net> To: Rui Paulo <rpaulo@freebsd.org> Cc: current@freebsd.org Subject: Re: Another clang problem Message-ID: <20101003140425.GA98803@oriental.arm.org> In-Reply-To: <9825922F-0808-4A60-97B7-2A6818FA409F@FreeBSD.org> References: <20101003134111.GA98699@oriental.arm.org> <9825922F-0808-4A60-97B7-2A6818FA409F@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Rui Paulo <rpaulo@freebsd.org> [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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101003140425.GA98803>