[SERVER-46299] SUSE15 C++ toolchain failure. Need binutils-2.32? Created: 21/Feb/20 Updated: 29/Oct/23 Resolved: 10/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc1 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Billy Donahue | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | |||||||||
| Sprint: | STM 2020-03-23, Dev Platform 2020-04-06, Dev Platform 2020-04-20 | ||||||||
| Participants: | |||||||||
| Description |
|
SUSE15 compiles are failing at the g++ configure check level with:
We might need binutils-2.32 instead of binutils-2.30. Apparently elfutils fixed a bug and binutils pre-2.32 relied on the buggy behavior. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 03/Apr/20 ] |
|
I tried doing an upgrade of the v3 toolchain to binutils-2.34 but was not successful. There appear to be incompatibilities between GCC 8 and such new binutils that I'm not sure how to resolve. Next week I will instead attempt to backport the fixes from https://sourceware.org/bugzilla/show_bug.cgi?id=23916 into binutils-2.30 and see if that works. |
| Comment by Brooke Miller [ 02/Apr/20 ] |
|
Thanks for the reminder acm! |
| Comment by Billy Donahue [ 25/Feb/20 ] |
|
This isn't a good time in our release cycle to debug the toolchain issues on SUSE 15, so I would like to just back out the SUSE15 AMI that's failing. Regenerating the SUSE15 buildimage AMI exposed this issue. our toolchain isn't going to work with up-to-date SUSE15. I believe this is caused by /usr/lib64/libc_nonshared.a(elf-init.oS): unable to initialize decompress status for section .debug_info The versions are slightly different for glibc-devel in the new SUSE15 AMI: The problem isn't with the libc but rather the toolchain that SUSE used to build it. |