Your message dated Thu, 31 Oct 2019 23:35:00 +0000
with message-id <>
and subject line Bug#943798: fixed in glibc 2.29-3
has caused the Debian Bug report #943798,
regarding old Arm ABI detection patch causing problems, time to remove?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Source: glibc
Version: 2.28-10
Severity: important

Hi folks,

It looks like my old Arm ABI detection patch for is causing
problems for people using LLVM. I've been contacted by a developer,
referring to a mailing list thread:

It looks like the LLVM version of strip is more aggressive than the
GNU binutils version, and this is causing problems - it's stripping
the .ARM.attributes data and that's causing problems with our extra
checks for the Tag_ABI_VFP_args setting. Whether that's a valid thing
to do or not is an argument for another day, I think... However,
checking with the bzip2 binaries that the reporter provided I can see
that they have the right ABI flag in the ELF header but we're still
running the extra ABI check:

(sid-armhf)steve@mjolnir:~/abi$ LD_PRELOAD=./ ./bzip2 
ERROR: object './' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
bzip2: I won't write compressed data to a terminal.
bzip2: For help, type: `bzip2 --help'.

(sid-armhf)steve@mjolnir:~/abi$ readelf -a | grep "^  Flags"
  Flags:                             0x5000400, Version5 EABI, hard-float ABI

I think this is wrong, and I can't think of why I didn't find this
earlier when I was working in this area. :-/

So: I think we have two sensible options:

1. I find time now to fix up to only do the extra check here if
   we think it's needed


2. Just remove the patch for extra check here - it was always the plan
   that this would go away after a while once people were unlikely to
   still be running binaries from the pre ELF-header toolchains.

Checking history, I can see that the binutils changes for those ELF
header changes landed in Debian back in Nov 2012. (Wow, time
flies!). Given that, I'd now be strongly in favour of just dropping the
patch in


as it's now safely obsolete. What do others think?

-- System Information:
Debian Release: 10.1
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.29-3

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
Samuel Thibault <> (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing

Hash: SHA512

Format: 1.8
Date: Thu, 31 Oct 2019 23:31:12 +0100
Source: glibc
Binary: glibc-doc glibc-source libc-bin libc-bin-dbgsym libc-dev-bin 
libc-dev-bin-dbgsym libc-l10n libc6 libc6-dbg libc6-dev libc6-dev-i386 
libc6-dev-x32 libc6-i386 libc6-i386-dbgsym libc6-pic libc6-udeb libc6-x32 
libc6-x32-dbgsym locales locales-all nscd nscd-dbgsym
Architecture: source
Version: 2.29-3
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers <>
Changed-By: Samuel Thibault <>
 glibc-doc  - GNU C Library: Documentation
 glibc-source - GNU C Library: sources
 libc-bin   - GNU C Library: Binaries
 libc-dev-bin - GNU C Library: Development binaries
 libc-l10n  - GNU C Library: localization files
 libc6      - GNU C Library: Shared libraries
 libc6-dbg  - GNU C Library: detached debugging symbols
 libc6-dev  - GNU C Library: Development Libraries and Header Files
 libc6-dev-i386 - GNU C Library: 32-bit development libraries for AMD64
 libc6-dev-x32 - GNU C Library: X32 ABI Development Libraries for AMD64
 libc6-i386 - GNU C Library: 32-bit shared libraries for AMD64
 libc6-pic  - GNU C Library: PIC archive library
 libc6-udeb - GNU C Library: Shared libraries - udeb (udeb)
 libc6-x32  - GNU C Library: X32 ABI Shared libraries for AMD64
 locales    - GNU C Library: National Language (locale) data [support]
 locales-all - GNU C Library: Precompiled locale data
 nscd       - GNU C Library: Name Service Cache Daemon
Closes: 943798
 glibc (2.29-3) unstable; urgency=medium
   [ Svante Signell ]
   * patches/hurd-i386/git-rlock.diff: New patch to add support for record
   [ Samuel Thibault ]
   * patches/hurd-i386/tg-locarchive.diff,tg-WRLCK-upgrade.diff: Remove, now
   * control: Bump hurd-dev dependency to get record locking RPC.
   * libc0.3.symbols.hurd-i386: Update accordingly.
   * patches/arm/unsubmitted-ldso-abi-check.diff: Remove obsolete patch.
     Closes: #943798.
 90f48d1758809cb7fd29a12b829439d058c82f36 8735 glibc_2.29-3.dsc
 d6377f5f0c2f3ac94b116196ec36e7885719ad2b 853764 glibc_2.29-3.debian.tar.xz
 f4c5edd6ffc97dff1846acaee47c46afca17eb01207234155e29345be15230e6 8735 
 13001db28f70be4d635617ec6ebbc6ea1da34199f06e84d1363100b816b5a2ea 853764 
 bf6c109f30eb78ec31b738f0bbb5b458 8735 libs required glibc_2.29-3.dsc
 66eacbc52a1d75ae6064f1c833042f76 853764 libs required 



--- End Message ---

Reply via email to