SRU: build with -fno-omit-frame-pointer

[Matthias Klose]

SRU:

  * SRU: LP: #2076024: Build with -fno-omit-frame-pointer.
  * Build loong64 packages on arm64 and ppc64el.
  * ld.bfd, ld.gold: When no package-metadata option is given, fall-back
    to the envvar ELF_PACKAGE_METADATA.

The first one enables the -fno-omit-frame-pointer flag on the architectures where it is the default.

The second one just builds packages which are already built on other architectures on two more architectues.

The third patch is a no-op, because ELF_PACKAGE_DATA is not set by default anywhere in noble. It gets used by the cross compiler packages to set the correct package name. Without it, cross compiler packages would look like being built from the gcc-N packages, not the gcc-N-cross packages.

These changes were part of a test rebuild of the main component on all architectures, with results at
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-noble-tc-noble.html
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-noble-noble.html

The first one is built with all proposed changes to the binutils, GCC, LLVM and Python packages, the second one is a reference test rebuild with unmodified release and updates pockets.

Comparing these, we find one progression, and some regressions.

- urwid, progression. builds with the updated packages, fails in the noble
  archive. Not further investigated.

- linux-* (11 packages). This is LP: #2081797, a configuration issue based
  on a GCC version. The fixed compiler already is in the noble release, but
  still identifies as 13.2.0. The kernel team is aware of that, and makes
  the fix of the next upload.
  A test build with the fix worked fine, and survived a reboot on an amd64
  laptop.

- gcc-14 fails in the archive, but is part of the planned updates. This is
  caused by some gnat 64bit time_t fixes.

- bpftrace is a build failure seen with the LLVM 18.1.8 update, however caused
  by some underlinking in bpftrace. The proposed fix should be SRU'd together
  with the LLVM update.

- There are some Python related failures, which still need to be investigated.
  These have to be addressed before the Python SRUs (doing that later than
  the binutils, GCC and LLVM updates). These are heat, pydantic,
  python-oslo-config, python-xmlschema and walinuxagent

The packages proposed as SRUs don't show regressions in their testsuites which are run during the builds.

[Łukasz Zemczak (sil2100)]

Hello Matthias, or anyone else affected,

Accepted binutils into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/binutils/2.42-4ubuntu2.3 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-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. 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 binutils (2.42-4ubuntu2.3) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

linux-ibm/6.8.0-1013.13 (amd64)

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/noble/update_excuses.html#binutils

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

Thank you!

[Matthias Klose (doko)]

checked the build logs that the flags are passed

[Matthias Klose (doko)]

the autopkg test regression is not caused by binutils, but by the newer gcc 13.3.0 version.
This is reported in LP: #2081797, and needs an adjustment in the kernel packages.

[Andreas Hasenack (ahasenack)]

I'm recording this comment just to show I saw this bug in my shift, but am not taking any action on it:
- devel task is still "new", and oracular was released today. What's the status in oracular+?
- there is no SRU template
- what's the test plan? The verification comment just says some build logs were checked
- there also seem to be at least two other bugs spawned off from this one, and potentially others too given the bug description and notices of regressions. What's going on? Why is it safe to continue without all those other bugs fixed? Shouldn't they all be tasks here?

As can be seen, many questions, and the lack of the standardized SRU template makes it more difficult to analyze.