SRU: rebuild libunwind with GCC 11.4

[Matthias Klose]

Reported in LP: #1997161

after updating GCC 11 in 22.04 LTS to 11.3, and now to 11.4, linking with the static libraries provided by libunwind-dev fails with:

lto1: fatal error: bytecode stream in file '/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libunwind-x86_64.a' generated with LTO version 11.2 instead of the expected 11.3

This happens, because gcc-11 bumped the LTO version in 11.3 (11.3.0-1ubuntu1~22.04), plus the static libraries are not stripped in the packaging.

Fixes could be to change the packaging, disable the LTO build for the package, or just rebuild with the new compiler.

For 22.04 LTS, the least invasive action seems to be the no-change rebuild.

To verify the packages: check that the package builds with the correct compiler version, and that the tests succeed during the build.

[Łukasz Zemczak (sil2100)]

Hello Matthias, or anyone else affected,

Accepted libunwind into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libunwind/1.3.2-2build2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted libunwind (1.3.2-2build2.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

linux-aws-5.19/5.19.0-1028.29~22.04.1 (arm64)
linux-aws-6.2/6.2.0-1006.6~22.04.1 (arm64)
linux-azure-5.19/5.19.0-1027.30~22.04.2 (arm64)
linux-gke/5.15.0-1037.42 (arm64)
linux-lowlatency/5.15.0-76.83 (arm64)
linux-lowlatency-hwe-5.19/5.19.0-1028.29~22.04.1 (arm64)
linux-nvidia-tegra/5.15.0-1014.14 (arm64)
linux-xilinx-zynqmp/5.15.0-1022.26 (arm64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#libunwind

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Matthias Klose (doko)]

the package successfully built. All the autopkg tests from the previous comment have been retried and succeeded.

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for libunwind has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package libunwind - 1.3.2-2build2.1

---------------
libunwind (1.3.2-2build2.1) jammy-proposed; urgency=medium

  * SRU: LP: #2025458. No change rebuild using GCC 11.4.

 -- Matthias Klose <email address hidden> Fri, 30 Jun 2023 10:07:20 +0200