[igt-dev] [PATCH i-g-t] scripts/example-debug-error: added script for debugging compilation errors on gitlab

[Kamil Konieczny]

Hi Mauro,

On 2023-09-19 at 09:14:28 +0200, Mauro Carvalho Chehab wrote:
> On Thu, 31 Aug 2023 19:02:45 +0200
> Kamil Konieczny <kamil.konieczny at linux.intel.com> wrote:
> 
> > Added example script to help quick start debugging compilation
> > errors seen on GitLab fdo when building new patch or patchset.
> > 
> > Cc: Petri Latvala <adrinael at adrinael.net>
> > Cc: Mauro Carvalho Chehab <mauro.chehab at linux.intel.com>
> > Signed-off-by: Kamil Konieczny <kamil.konieczny at linux.intel.com>
> > ---
> >  scripts/example-debug-error.sh | 32 ++++++++++++++++++++++++++++++++
> >  1 file changed, 32 insertions(+)
> >  create mode 100755 scripts/example-debug-error.sh
> > 
> > diff --git a/scripts/example-debug-error.sh b/scripts/example-debug-error.sh
> > new file mode 100755
> > index 000000000..755c90a25
> > --- /dev/null
> > +++ b/scripts/example-debug-error.sh
> > @@ -0,0 +1,32 @@
> > +#!/bin/sh
> > +# SPDX-License-Identifier: MIT
> > +#
> > +# Copyright © 2023 Intel Corporation
> > +#
> > +# When you see compilation error in fdo GitLab follow link with
> > +# error to find out used registry, it should be at top of log,
> > +# for example:
> > +# Using Docker executor with image registry.freedesktop.org/gfx-ci/igt-ci-tags/build-debian-arm64:commit-1af4386ff3086df670e10af3a2bfd89993af3b0a
> > +#
> > +# Take registry and put it into POD_IGT var below (default will use debian build for amd64/x64):
> > +#
> > +POD_IGT=registry.freedesktop.org/gfx-ci/igt-ci-tags/build-debian:commit-1af4386ff3086df670e10af3a2bfd89993af3b0a
> > +
> > +mkdir -p /tmp/igt-build
> > +cp -R * /tmp/igt-build/
> > +sudo podman run -i -t -v /tmp/igt-build/:/opt/builds --privileged ${POD_IGT}
> > +
> > +# you can debug now with:
> > +#
> > +# cd /opt/builds
> > +# meson build
> > +# ninja -C build
> > +#
> > +# or for cross-compilation for arm64 (for other arch remember to change registry):
> > +#
> > +# export PKG_CONFIG_PATH=/usr/lib/aarch64-linux-gnu/pkgconfig/
> > +# meson --cross-file meson-cross-arm64.txt build
> > +# ninja -C build
> 
> There are steps missing here, as the downloaded image doesn't contain the
> cross-compiler toolchain to install the packages listed at
> Dockerfile.build-debian-arm64.

You are right, I forgot to add other image for cross-compilation.
I also spotted repeated string in script, I will change it to
other variable.

Regards,
Kamil

> 
> On my tests, those steps are needed:
> 
> 	dpkg --add-architecture arm64
> 	apt-get update --allow-releaseinfo-change
> 	apt-get install -y gcc-aarch64-linux-gnu libatomic1:arm64 libpciaccess-dev:arm64 libkmod-dev:arm64 libprocps-dev:arm64 libunwind-dev:arm64 libdw-dev:arm64 zlib1g-dev:arm64 liblzma-dev:arm64 libcairo-dev:arm64 libpixman-1-dev:arm64 libudev-dev:arm64 libgsl-dev:arm64 libasound2-dev:arm64 libjson-c-dev:arm64 libcurl4-openssl-dev:arm64 libxrandr-dev:arm64 libxv-dev:arm64 libdrm-dev:arm64 qemu-user qemu-user-static
> 
> Note: --allow-releaseinfo-change is needed due to the downloaded
> from registry.freedesktop.org is already EOL.
> 
> Still, something else is missing, as ld is failing with:
> 
> /usr/lib/gcc-cross/aarch64-linux-gnu/8/../../../../aarch64-linux-gnu/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libm.a when searching for -lm
> collect2: error: ld returned 1 exit status
> ninja: build stopped: subcommand failed.
> 
> Please fix the instructions.
> 
> Regards,
> Mauro