Custom compile of gcc 9.2.1 toolchain, not relocatable

Hi!

I have made a custom compilation of the gcc 9.2.1 toolchain (https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads)

using this manifest : gcc-arm-arm-none-linux-gnueabihf-abe-manifest.txt and following the ABE build guide in the link above.

Everything works as expected, and I get a compiler toolchain out in the end. It is, however, not relocatable! I cannot move the toolchain to another location, as

it seems like the sysroot path in the toolchain is hardcoded. I have wrapped the ABE build in a simple docker image, instead of building it on my own PC, but the sysroot of the resulting toolchain that I extract from the docker image, still points to a fixed path inside the docker container. This means that I cannot run the toolchain, outside the docker container, or move it to any other location for that matter.

Ex:

       arm-none-linux-gnueabihf-gcc -print-sysroot ----------> /build/builds/destdir/x86_64-unknown-linux-gnu/arm-linux-gnueabi/libc

Is there a config option I am missing in the manifest somewhere? The manifest I built from is 100& as-is. I did not edit it. The toolchain supplied on the link above that is prebuilt, is relocatable, as shown by this sysroot:

       arm-none-linux-gnueabihf-gcc -print-sysroot ----------> /my/user/location/environments/arm_8.2.1_cross/compiler/bin/../arm-linux-gnueabi/libc

I can move this compiler around, and the sysroot changes. My own build of the toolchain does not do this.

What gives? :) Any help would be greatly appreciated.