I actually wrote about this very issue in this thread before.

In such case I simply build a newer libdrm package for Debian and install it system wide. It's easier than pointing to some custom libdrm location when building. In your case you need both regular and dev package for building Mesa.

I wrote down for myself how to do it, so here is my note:

Let's say Debian still has older libdrm (let's say 2.4.97), and you want a newer one (2.4.99).

Make sure to have devscripts package installed.

wget https://dri.freedesktop.org/libdrm/libdrm-2.4.99.tar.gz -O $HOME/downloads/libdrm-2.4.99.tar.gz

mkdir -p $HOME/build/libdrm
cd $HOME/build/libdrm
sudo apt-get build-dep libdrm
apt-get source libdrm
cd libdrm-2.4.97
uupdate ~/downloads/libdrm-2.4.99.tar.gz
cd ../libdrm-2.4.99
dpkg-buildpackage -us -uc -nc

# You might need to add some missing symbol definitions along the way to match new upstream

To build 32-bit variant, use:

apt-get build-dep -a i386 libdrm
dpkg-buildpackage -a i386 -us -uc -nc

# You might need to install some gcc packages manually, since apparently build-dep -a i386 is not enough.

# Possibly dpkg --force-overwrite -i is needed, to work around changelog
conflicts in packages.

Quoting: ShmerlI actually wrote about this very issue in this thread before.

In such case I simply build a newer libdrm package for Debian and install it system wide. It's easier than pointing to some custom libdrm location when building. In your case you need both regular and dev package for building Mesa.

I wrote down for myself how to do it, so here is my note:

Thanks for the tips, I went ahead and compiled/packaged the new libs. Installation went smooth and the Mesa config did get to the next step. I still have a few outdated packages to work on but getting there.

Considering how old Debian 9 is, all the signs would tell me to go for something newer. It's been a fun learning experience though so I'll keep digging :)

Sure, upgrade to Debian testing, and avoid the mess. Even there such stuff as above is needed during freeze periods, that's why I was doing it. But for the most part it's up to date.

They did enable bulk moves, but afetr 5.4-rc1 (i.e. 5.4-rc2 has it). I can't test Aco yet, due to it being still quite buggy with Navi.

Quoting: ShmerlThey did enable bulk moves, but afetr 5.4-rc1 (i.e. 5.4-rc2 has it). I can't test Aco yet, due to it being still quite buggy with Navi.

Maybe it improved a little bit: https://www.phoronix.com/scan.php?page=news_item&px=RADV-Navi-GFX10-ACO-Lands

Not yet. It's still work in progress.

Quoting: GuestMama mia

Does Star Citizen work for you with latest Wine/dxvk? I couldn't run the updater for it at all. See here.

Shmerl,

what you you got going for a meson configure line these days? if you compile it yourself.
-Dvulkan-overlay-layer=true doesn't work anymore. Do you know how debian configures it?

Quoting: sr_ls_boyShmerl,

what you you got going for a meson configure line these days? if you compile it yourself.
-Dvulkan-overlay-layer=true doesn't work anymore. Do you know how debian configures it?

You can check my script to get the idea:

https://gist.github.com/shmerl/f4e5f76871239158cf083e37c5da56f4

I have something like this:

-Dvulkan-layers="['device-select','overlay']"

To check how Debian does it, I usually go to the tracker page: https://tracker.debian.org/pkg/mesa

Then look for the build logs link (buildd: logs): https://buildd.debian.org/status/package.php?p=mesa

Then select amd64 and click "Installed" (pretty obscure link on that page):
https://buildd.debian.org/status/fetch.php?pkg=mesa&arch=amd64&ver=22.2.0%7Erc2-1&stamp=1660228051&raw=0

You can find Meson invocation there.

I use that to periodically update my script if things change too much.

Last edited by Shmerl on 17 Aug 2022 at 11:32 pm UTC