When debian packaging built mesa 18.3.2-1 with meson build system using the following configuration parameters:
dri.pc got the following incorrect dridriverdir:
which caused xorg-server built against it to try to dlopen the glx libraries from the wrong path since xorg-xserver's configure uses pkg-config --variable=dridriverdir dri to get the path to dlopen glx libraries from.
Removing the two -Ddri-*-path configuration parameters from debian/rules seems to have fixed the problem which has also been reported here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922807
Looks like during meson configuration you are also using --prefix=/usr
So if at this moment as workaround option dri-drivers-path will exclude a 'prefix' from path it should work, like:
Also patch to mesa proposed: https://gitlab.freedesktop.org/mesa/mesa/merge_requests/285
Could you, please, try if it fixes issue?
AFAICT there are two issues here.
1. the prefix wrongfully added to the custom variable
2. the custom variable can be a list of paths separated by colon, yet only the first one ends up in dri.pc
Perhaps one process of prefixing (1) also broke the multiple paths (2)?
Should be fixed with the following. Expect the commit to land in 18.3 and 19.0 in due time.
Author: Sergii Romantsov <email@example.com>
Date: Thu Feb 21 10:28:11 2019 +0200
dri: meson: do not prefix user provided dri-drivers-path
The user can select the location where there dri drivers