Mesa is installed but it show old version

[zRevengee]

i created a bash script to automate the installation of a 64bit chroot and compiling in it the latest mesa 20 from github for make Dolphin playable, the issue is this:
my script work, i mean it install mesa 20 without errors but when i try to get info or playing a game on dolphin it show that mesa is 18.3.

this is part of the script :

Code: Select all

echo "Updating and Upgrading"
echo
sudo apt-get update && sudo apt-get upgrade -y
echo
echo "creating 64bit chroot"
echo
sudo apt-get install -y debootstrap schroot
echo
cat << EOF | sudo tee /etc/schroot/chroot.d/pi64 >/dev/null
[pi64]
description=Debian Buster arm64
type=directory
directory=/srv/chroot/pi64
users=pi
root-groups=root
profile=desktop
personality=linux
preserve-environment=true
EOF
echo
echo "runtime dependencies to chroot"
echo
sudo debootstrap --arch=arm64 buster /srv/chroot/pi64
echo
sudo sudo schroot -c pi64 -- apt-get install -y sudo curl mesa-utils xz-utils libqt5widgets5 libevdev2 libudev1 libasound2 libbluetooth3 libopengl0 libglu1-mesa
echo
echo "entering chroot"
echo
schroot -c pi64
echo
echo "Mesa Dependencies"
echo
sudo apt build-dep libgl1-mesa-dri
echo
sudo apt install automake libtool bison flex gettext libdrm-dev libexpat1-dev libudev-dev libx11-xcb-dev libxcb-dri3-dev libxcb-dri2-0-dev libxcb-glx0-dev libxcb-xfixes0-dev libxcb-present-dev libxcb-sync-dev libxshmfence-dev libxdamage-dev libxext-dev libxfixes-dev python-mako x11proto-present-dev x11proto-dri3-dev x11proto-dri2-dev x11proto-gl-dev mesa-utils
echo
echo "Downloading latest mesa version"
echo
sudo mkdir /temp && cd /temp
echo
sudo apt-get install git
echo
sudo git clone https://gitlab.freedesktop.org/mesa/mesa.git
echo
cd mesa
echo
sudo apt-get install meson
echo
sudo apt-get install python3-pip
echo
sudo apt-get install python3-mako
echo
sudo apt-get install pkg-config libwayland-dev wayland-protocols libwayland-egl-backend-dev libxxf86vm-dev x11-xserver-utils libxrandr-dev
echo
sudo pip3 install --upgrade meson
echo
sudo meson build
echo
sudo meson configure build/
echo
sudo meson --prefix=/usr \
echo
sudo meson configure -Dgallium-drivers=swrast,kmsro,v3d,vc4 \
echo
sudo meson configure -Dglx=dri \
echo
sudo meson configure -Dbuildtype=release \
echo
sudo meson configure -Degl=true \
echo
sudo meson configure -Dgles1=true \
echo
sudo meson configure -Dgles2=true \
echo
sudo meson configure -Dplatforms=x11,drm \
echo
sudo ninja -C build/
echo
sudo ninja -C build/ install

opening dolphin show that is installed mesa 18.3

Pi 4 4GB with old kernel 4.19

[topguy]

So where exactly is the Dolphin running ? In the chroot or not ?

[zRevengee]

it is running in chroot, Dolphin-emu can't run outside of chroot, it's a 64bit program

[topguy]

So we can ignore everyting outside of the chroot..

Then my guess its about the paths defined for "ld" ( dynamic-linker ) to look.
Your build of Mesa might put the libraries in "/usr/local/lib" for example but there might be nothing in "/etc/ld.so.conf" or "/etc/ld.so.conf.d/" that tells the linker to look there.

Running the "ldd" command on the Dolphin executable should list all the libraries and the path to them.

"ldconfig -v" ( as root ) will also list all libraries ld know about. "ldconfig" is also used to rebuild the list if you change the paths.

[zRevengee]

ldd usr/local/bin/dolphin-emu

not a dynamic executable



edit nvm , i executed in chroot and i show that libs are in /lib/aarch64-linux-gnu/libName.so

[topguy]

You have to figure out where the mesa libraries was installed...