Bug 1774483 - [.gnu.build.attributes]: corrupt GNU build attribute note: wrong note type: bad value
Summary: [.gnu.build.attributes]: corrupt GNU build attribute note: wrong note type: b...
Keywords:
Status: ASSIGNED
Alias: None
Product: Fedora
Classification: Fedora
Component: binutils
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nick Clifton
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-20 12:02 UTC by Harald Reindl
Modified: 2019-11-21 13:21 UTC (History)
6 users (show)

Fixed In Version: binutils-2.31.1-35.fc30
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Harald Reindl 2019-11-20 12:02:15 UTC
what the hell is that affecting most local specfiles using "strip -s --strip-unneeded" for years?

binutils-2.31.1-34.fc30.x86_64

strip:/home/builduser/rpmbuild/BUILDROOT/httpd-2.4.41-2.170.161.0.fc30.20191120.rh.sandybridge.x86_64/usr/lib64/libaprutil-1.so.0.6.1[.gnu.build.attributes]: corrupt GNU build attribute note: wrong note type: bad value
error: Bad exit status from /var/tmp/rpm-tmp.huNUkC (%install

Comment 1 Nick Clifton 2019-11-20 15:59:47 UTC
Hi Harald,

  Sorry - this was a bug introduced with the -34 release, which should now be fixed with the -35 release.

  Essentially what happened was that I added code to further reduce the size of stripped binaries by compacting the annobin data held in the .gnu.build.attributes section.  But I made a mistake and ended up generating corrupt data instead.  Ho hum.

  Please try using the -35 release and let me know if that solves the problem for you.

Cheers
  Nick

Comment 2 Lars Gullik Bjønnes 2019-11-21 13:14:17 UTC
I seemingly see the same problem with fc31, with the update to binutils.x86_64 2.32-26.fc31 (from -24)

Comment 3 Nick Clifton 2019-11-21 13:21:23 UTC
(In reply to Lars Gullik Bjønnes from comment #2)
> I seemingly see the same problem with fc31, with the update to
> binutils.x86_64 2.32-26.fc31 (from -24)

True, but the newer releases (-27 onwards) should fix that.


Note You need to log in before you can comment on or make changes to this bug.