[Bug 2031495] Re: glibc 2.38/armf: can't find libgcc_s.so.1 during tests

Launchpad Bug Tracker 2031495 at bugs.launchpad.net
Sat Nov 18 10:13:16 UTC 2023


This bug was fixed in the package glibc - 2.38-3ubuntu1

---------------
glibc (2.38-3ubuntu1) noble; urgency=medium

  * debian/patches/git-updates.diff: update from upstream stable branch
    Dropped changes, superseded by the upstream git updates:
    - debian/patches/CVE-2023-4911.patch: terminate immediately if end of
      input is reached in elf/dl-tunables.c.
    - d/p/u/0001-Fix-leak-in-getaddrinfo-introduced-by-the-fix-for-CV:
      Cherry-picked to fix a regression in one of the previous CVE fixes
  * Merge 2.38-3 from Debian experimental
    Dropped changes, included in Debian:
    - debian/patches/hurd-i386/git-powerpc-longjmp.diff: Fix build after chk
      hidden builtin fix.
  * Drop d/p/lp2032624.patch as advised by upstream.
    Downstream users will have to actually implement those types or stop
    pretending they're GCC. (LP: #2032624)
  * d/p/lp2031495.patch: fix test suite on armhf for -prof variant
    (LP: #2031495)
  * d/control.in/i386: fix math-vector-fortran.h file move (LP: #2039234)

 -- Simon Chopin <schopin at ubuntu.com>  Mon, 23 Oct 2023 18:54:07 +0200

** Changed in: glibc (Ubuntu)
       Status: In Progress => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4911

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/2031495

Title:
  glibc 2.38/armf: can't find libgcc_s.so.1 during tests

Status in glibc package in Ubuntu:
  Fix Released

Bug description:
  [impact]

  The glibc testsuite has been broken on armhf for mantic, this needs to
  be fixed to help ensure future SRUs won't introduce unseen regressions
  on that arch.

  [test case]

  Ensure that the armhf autopkgtests are successful in -proposed, and
  that the testsuite has been entirely run

  [regression potential]

  While there aren't any direct regression risks at runtime, if this
  patch is wrong we would potentially have the tests importing the wrong
  versions of the library, resulting in hard to debug test failures.

  [original report]
  glibc 2.38-1ubuntu3 tests fail with the following failure (on multiple instances):

  4112s /tmp/autopkgtest.rMSc2W/build.aCV/src/build-tree/armhf-
  prof/elf/tst-pldd: error while loading shared libraries:
  libgcc_s.so.1: cannot open shared object file: No such file or
  directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2031495/+subscriptions




More information about the foundations-bugs mailing list