On 20.04.2016 03:39, Emil Velikov wrote: > On 19 April 2016 at 15:47, Chuck Atkins <chuck.atk...@kitware.com> wrote: >> This still doesn't quite give what you want. One can also have an llvm with >> component shared libs. So there's three different options for llvm library >> configurations: a single shared lib, component shared libs, or component >> static libs. > From the three - only single shared lib and component static libs are > supported.
Right, in fact I understand that the component shared libs are only intended for LLVM developers, and IME trying to use them causes various undesirable side effects. > Personally I'm leaning that we ought to go with the latter only... Esp > considering the problems that people tend to have with mesa + steam, > every so often. Steam and some Steam games unnecessarily overriding system libraries with stale versions causes problems with other libraries as well, so it requires other solutions than linking LLVM statically anyway. > Tom, what is your view on the topic - are you ok with us switching > back to static one and/or nuking the shared one ? For all the reasons Tom mentioned, I kindly ask to leave the possibility of dynamically linking LLVM. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
