Build wrapper fails to open libinterceptor shared object when cross-compiling for ARM

SonarQube Server / Community Build
1

Versions used:
SonarQube Server: Developer Edition Version 9.9.1 (build 69595)
Build wrapper: x86, 6.41
OS of host: RHEL 7.9, 8.9

We are trying to use the build wrapper on a C project that cross-compiles for the ARM architecture, but we are getting the following error message each time it tries to build a compilation unit:

ERROR: ld.so: object ‘/user/kpowel01/jupiter/.sonar/build-wrapper-linux-x86/libinterceptor-${PLATFORM}.so’ from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

The build wrapper directory contains:
image

This error can be triggered with the following command run from either of our machines (one is RHEL 7.9, the other RHEL 8.9), outside of any docker containers:

~/jupiter/.sonar/build-wrapper-linux-x86/build-wrapper-linux-x86-64 --out-dir ~/jupiter/.sonar/bw-output/ ./arm aarch64-poky-linux-gcc --sysroot=/opt/poky/2.4/sysroots/aarch64-poky-linux -O2 -pipe -MMD -c -o test.o test.c

test.c is a minimal .c file with an empty main function. In the current working directory, we have a script named “arm” that contains the following:

#!/bin/sh
unset LD_LIBRARY_PATH
. /opt/poky/2.4/environment-setup-aarch64-poky-linux
$*

The goal is to get SonarQube to run on our code in a Docker container, but the issue we’re facing also happens when the build wrapper is run outside of any containers.

EDIT: we found out that if we use the poky2.5.3 toolchain instead of poky2.4, this issue does NOT occur. However, upgrading our code to use the poky2.5.3 toolchain would be a lot of work.

2

Hey @ken437!

For what it’s worth we have an open ticket to better support toolchains sourced from Yocto. It’s a good piece of info that a newer version of the toolchain appears to work.

In the meantime, I would suggest two things:

First, you should upgrade to the current LTA (long-term active version) at your earliest convenience. Your upgrade path is:

9.9.1 → 2025.1

You may find these resources helpful:

Secondly, with the new LTA, you can benefit from AutoConfig, which allows you to perform an analysis without involving the build warpper (or a compilation) at all.