> On Jan 1, 2019, at 11:23 AM, Martin Husemann <mar...@duskware.de> wrote:
>
> Yeah (and to waste more than an additional hour in a full build of
> NetBSD) - but then we need a working plan how to provide libllvm as
> part of the installed system, not only headers for building libmesa.
I'm not arguing the merits of it one way or the other, just trying to explain
why it's needed in this particular instance. I agree that the issues involved
here are thorny (especially if LLVM isn't providing API / ABI stability from
release to release), and there are a lot of trade-offs to be weighed.
But I really just wanted to point out that this isn't really a toolchain issue.
IMO, the best way to handle this situation is to decouple "LLVM used to
provide JIT / VM services to system libraries or other subsystems" from "LLVM
used as compiler toolchain component". The former, which is what Maya needs in
this case, is something that can be updated on a different frequency from the
latter (at the cost of source tree bloat, but whatever, not that big of a
deal), and can be narrowed in scope (don't necessarily need the language
front-ends or CPU-target back-ends that the normal compiler toolchain requires).
-- thorpej
