Another clang problem

Derek Tattersall dlt at
Sun Oct 3 14:04:28 UTC 2010

* Rui Paulo <rpaulo at> [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  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 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. 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 at		dlt666 at		 dtatters at

More information about the freebsd-current mailing list