On Wed, 2018-02-28 at 18:53 +0100, Gert Wollny wrote:
> Am Mittwoch, den 28.02.2018, 17:52 +0200 schrieb Andres Gomez:
[...]
> >
+ test -f /usr/bin/llvm-config && ln -s /usr/bin/llvm-config
> > $HOME/prefix/bin
>
> I'm not sure how the toolchain packages on travis are created and maybe
> w
Am Mittwoch, den 28.02.2018, 17:52 +0200 schrieb Andres Gomez:
> Travis CI has moved to LLVM 5.0, and meson is detecting automatically
> the available version in /usr/local/bin based on the PATH env
> variable
> order preference.
>
> As for 0.44.x, Meson cannot receive the path to the llvm-config
Reviewed-by: Juan A. Suarez
On Wed, 2018-02-28 at 17:52 +0200, Andres Gomez wrote:
> Travis CI has moved to LLVM 5.0, and meson is detecting automatically
> the available version in /usr/local/bin based on the PATH env variable
> order preference.
>
> As for 0.44.x, Meson cannot receive the pat
Quoting Andres Gomez (2018-02-28 07:52:06)
> Travis CI has moved to LLVM 5.0, and meson is detecting automatically
> the available version in /usr/local/bin based on the PATH env variable
> order preference.
>
> As for 0.44.x, Meson cannot receive the path to the llvm-config binary
> as a configur
On Wednesday, 2018-02-28 17:52:06 +0200, Andres Gomez wrote:
> Travis CI has moved to LLVM 5.0, and meson is detecting automatically
> the available version in /usr/local/bin based on the PATH env variable
> order preference.
>
> As for 0.44.x, Meson cannot receive the path to the llvm-config bina
Travis CI has moved to LLVM 5.0, and meson is detecting automatically
the available version in /usr/local/bin based on the PATH env variable
order preference.
As for 0.44.x, Meson cannot receive the path to the llvm-config binary
as a configuration parameter. See
https://github.com/mesonbuild/meso