[Mesa-dev] [PATCH] meson: Print a message about why a libdrm version was selected

Dylan Baker dylan at pnwbakers.com
Wed Sep 5 17:36:47 UTC 2018


Quoting Emil Velikov (2018-09-05 03:25:06)
> On 4 September 2018 at 22:47, Dylan Baker <dylan at pnwbakers.com> wrote:
> > We require a single version of libdrm for all of our libdrm
> > dependencies (core and driver), but the way this is structured can make
> > the error message less than helpful, as one driver might be the one
> > setting the libdrm requirement, while another might be the one that
> > generates the version failure.
> >
> > This adds a simple message to the output announcing which libdrm module
> > set the version, which might be more helpful.
> >
> Recently when libdrm_amdgpu was bumped, I noticed that it's version
> was still imposed, even though I was building only classic i965.
> Both gallium and vulkan drivers were explicitly disabled.
> 
> Can you please look into that, if you haven't already.
> 
> Thanks
> Emil

I can't reproduce this. I set the amdgpu version to 2.4.1000 (to ensure that I
couldn't fulfill it), then ran:
meson build -Dgallium-drivers= -Dvulkan-drivers= -Ddri-drivers=i965

Things worked fine. You didn't happen to have radv enabled did you? That
also pulls in libdrm_amdgpu.

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


More information about the mesa-dev mailing list