======================
> BUILD_SHARED_LIBS is only recommended for use by LLVM developers.
> If you want to build LLVM as a shared library, you should use the LLVM_BUILD_LLVM_DYLIB option.
> =============================================================================================
> 
> So upstream DOES NOT RECOMMEND to build shared libs to users!!!
I am curious about the motivation.

JFYI, shared llvm libs are required for lot of things.  The incomplete
list of examples that I am aware of are dri drivers and ispc Intel compiler.

> 
> Why FBSD use shared libs for LLVM in ports and now in base!???
> 
> @brooks - why do you do that?
> 
> 
> > The implied load on rtld is something that could be handled: there is
> > definitely no need to have such huge surface of exported symbols on
> > both libllvm and esp. libclang. Perhaps by default the internal
> > libraries can use protected symbols, normally C++ do not rely on
> > interposing. But such 'fixes' must occur at upstream.
> > 
> > So far all the clang toolchain changes were aligning it with what the
> > llvm project does.
> > 
> 
> No, upstream does not recommend to use shared libs to llvm users.