• State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 21 subscribers
  • Views 1830 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

No build-id on libraries from the Linux x86_64 gcc 11.3 toolchain

Eric

I downloaded the latest stable toolchain published for Linux x86_64, aarch64: arm-gnu-toolchain-11.3.rel1-x86_64-aarch64-none-linux-gnu.tar.xz

The libraries from this toolchain do not have a build-id which messes with some of our workflows, E.g., we can't do a proper backtrace analysis with tools like Sentry.

To illustrate:

$ file ./arm-gnu-toolchain-11.3.rel1-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/lib64/libc.so.6
./arm-gnu-toolchain-11.3.rel1-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/lib64/libc.so.6: ELF 64-bit LSB shared object, ARM aarch64, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, with debug_info, not stripped

Notice how there is no build-id listed there. For contrast, here is the output of the file command for another toolchain which does include build-ids:

$ file ./arm-none-linux-gnueabihf/libc/lib/libc-2.28.so
./arm-none-linux-gnueabihf/libc/lib/libc-2.28.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, BuildID[sha1]=d6f3fa913c453c25d2c115730ea34f4a04855dd7, for GNU/Linux 4.18.20, with debug_info, not stripped

I'm wondering if it would be possible to publish a new version of gcc 11.3 but with build ids. 

Thanks,

Eric.

0