Quoting Emil Velikov (2017-12-15 09:35:03)
> On 15 December 2017 at 16:49, Eric Engestrom <eric.engest...@imgtec.com> 
> wrote:
> > On Friday, 2017-12-15 17:17:55 +0100, Juan A. Suarez Romero wrote:
> >> Travis CI has moved to LLVM 5.0, and meson is detecting automatically
> >> the available version.
> >>
> >> So just let's change to LLVM 5.0 for this case.
> >
> > I thought we were using 3.9 on purpose, to test our minimum required
> > llvm version?
> >
> > I think the proper fix would be to add a `-D llvm-version=3.9` option
> > and use that in the dependency() check.
> >
> Allow me to suggest and alternative solution:
> 
> Feed in the llvm-config name (aka LLVM_CONFIG) like we do for scons
> and autotools.
> It will provide some nice consistency, plus it will allow for easier
> selection as path and version.
> 
> Not to mention that distributions (Debian for example) allow multiple
> versions to coexist, naming the binary - llvm-config-$version.
> 
> -Emil

I don't object to that solution, but it would require a change to upstream
meson, which currently doesn't have support for passing an explicit binary to
the dependency call. It would/will take some time for that to move through
review and would not be available until 0.45.0 at the earliest. Since 0.44.0
was released less than a week ago I would not expect 0.45 until mid January at
the earliest.

I think the easiest immediate solution would be to set the path environment
variable to not include /usr/local, or to use a symlink to mask the version in
/usr/local with the version that we want to use.

Attachment: signature.asc
Description: signature

_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Reply via email to