[Mesa-dev] autotools/meson transition: meson uses hardcoded list of llvm-config binaries, FTBFS with new upstream LLVM (development) versions

[Kai Wasserbäch]

Hey,
I just discovered that meson hardcodes the list of llvm-config binary names to
try in mesonbuild/dependencies/dev.py, line 214ff ([0]). This is breaking now
since LLVM upstream switched to version 9 and branched version 8 of to become a
stable release soon. See [1] for the upstream ticket I filed about this.

The hardcoded list seems rather fragile, and I would prefer if the default
behaviour of meson improves to the point, where the default build ("use newest
LLVM") doesn't depend on new meson releases or manual overrides before meson is
made mandatory for building Mesa.

Is this a sentiment shared by others?

Cheers,
Kai


[0]
<https://github.com/mesonbuild/meson/blob/master/mesonbuild/dependencies/dev.py#L214>
[1] <https://github.com/mesonbuild/meson/issues/4802>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20190119/a4fae516/attachment.sig>