This is neither a for or against, but I thought I'd add this to the discussion.
Currently meson only supports using LLVM as a shared library, so this is going to make the meson build and the autotools build do different things by default. I understand that meson is still in development and no distros will use it for a while yet (the only people who currently can are anv and radv devs), but it sounds like from what Tom and Michel are saying LLVM has this issue solved, and having the two build systems do something different by default seems less than ideal. We can add support to meson for statically linking with LLVM if we need to (I wrote the LLVM dependency handling for meson, so its shortcomings are my fault). Dylan Quoting Michel Dänzer (2017-10-05 06:33:09) > On 05/10/17 12:19 PM, Emil Velikov wrote: > > From: Emil Velikov <emil.veli...@collabora.com> > > > > A while back Michel reported that LLVM has symbol versioning to avoid > > symbol collisions. Based on observations LLVM 5.0 is the first upstream > > version to actually has it. > > Not exactly. Adam Jackson originally added symbol versioning in LLVM 3.6 > (in SVN r214418), but it was only effective when LLVM was built with > autotools. As of 5.0, it's effective with cmake as well. > > > > Since symbol collisions do come up again and again (fortunately not so > > often) let's flip the switch back to static. > > It seems a bit weird to make this change now, that LLVM is solving the > issue for good. But I don't feel strongly about it. > > > -- > Earthling Michel Dänzer | http://www.amd.com > Libre software enthusiast | Mesa and X developer > _______________________________________________ > mesa-stable mailing list > mesa-sta...@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-stable
signature.asc
Description: signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
