Bug 1916925 - /usr/bin/ld.gold: warning: /usr/lib/gcc/x86_64-redhat-linux/11/../../../../lib64/Scrt1.o: unknown program property type 0xc0008002 in .note.gnu.property section
Summary: /usr/bin/ld.gold: warning: /usr/lib/gcc/x86_64-redhat-linux/11/../../../../li...
Alias: None
Product: Fedora
Classification: Fedora
Component: binutils
Version: 33
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Nick Clifton
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2021-01-15 20:29 UTC by Michael Catanzaro
Modified: 2021-11-05 02:34 UTC (History)
10 users (show)

Fixed In Version: binutils-2.35-18.fc33, binutils-2.35.1-24.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-11-05 02:34:21 UTC
Type: Bug

Attachments (Terms of Use)

Description Michael Catanzaro 2021-01-15 20:29:15 UTC
Description of problem: I noticed WebKit builds recently (yesterday) started failing only on x86_64, during gtk-doc generation. Problem is ld.gold has started printing some warning, and any warning during doc generation causes the build to fail (it usually means the docs are broken).

For now, I'll switch WebKit to use ld.bfd as a workaround, but that means debug fission will be disabled.

Version-Release number of selected component (if applicable): binutils-gold-2.35.1-21.fc34

How reproducible: Always

Steps to Reproduce:
1. sudo update-alternatives --set ld /usr/bin/ld.gold
2. Link anything, e.g. a hello world program. The warning will be printed.
3. Reset to original state when done testing: sudo update-alternatives --set ld /usr/bin/ld.bfd

Actual results:

/usr/bin/ld.gold: warning: /usr/lib/gcc/x86_64-redhat-linux/11/../../../../lib64/Scrt1.o: unknown program property type 0xc0008002 in .note.gnu.property section

Expected results: No warning

Additional info: The capital of Vermont is Montpelier!

Comment 1 H.J. Lu 2021-01-18 13:43:43 UTC
This has been fixed on binutils 2.36 branch by

commit 586e30940e640f67bd55bd72e1d1355a4faf8079
Author: H.J. Lu <hjl.tools>
Date:   Tue Oct 13 05:20:49 2020 -0700

    gold: Update GNU_PROPERTY_X86_XXX macros
    This patch updates GNU_PROPERTY_X86_XXX macros for gold:
    1. GNU_PROPERTY_X86_UINT32_AND_XXX: A 4-byte unsigned integer property.
    A bit is set if it is set in all relocatable inputs:
     #define GNU_PROPERTY_X86_UINT32_AND_LO      0xc0000002
     #define GNU_PROPERTY_X86_UINT32_AND_HI      0xc0007fff
    2. GNU_PROPERTY_X86_UINT32_OR_XXX: A 4-byte unsigned integer property.
    A bit is set if it is set in any relocatable inputs:
     #define GNU_PROPERTY_X86_UINT32_OR_LO    0xc0008000
     #define GNU_PROPERTY_X86_UINT32_OR_HI    0xc000ffff
    3. GNU_PROPERTY_X86_UINT32_OR_AND_XXX: A 4-byte unsigned integer property.
    A bit is set if it is set in any relocatable inputs and the property is
    present in all relocatable inputs:
     #define GNU_PROPERTY_X86_UINT32_OR_AND_LO   0xc0010000
     #define GNU_PROPERTY_X86_UINT32_OR_AND_HI   0xc0017fff
    and GNU_PROPERTY_X86_FEATURE_2_XXX bits.
    and GNU_PROPERTY_X86_ISA_1_NEEDED are updated to better support targeted
    processors since GNU_PROPERTY_X86_ISA_1_?86 aren't isn't very useful.
    A new set of GNU_PROPERTY_X86_ISA_1_XXX bits are defined.  The previous
    GNU_PROPERTY_X86_ISA_1_XXX macros are deprecated and renamed to

Comment 2 Nick Clifton 2021-01-19 10:00:23 UTC
This should be fixed in binutils-2.35-18.fc33.

Comment 3 Kevin Kofler 2021-01-20 02:13:52 UTC
I'm also getting this on Rawhide and it breaks qt5-qtwebengine builds.

Comment 4 Kevin Kofler 2021-01-20 02:19:29 UTC
This is hindering my attempts to fix a QtWebEngine issue, see:

Comment 5 Nick Clifton 2021-01-20 10:27:16 UTC
(In reply to Kevin Kofler from comment #4)
Which version of the binutils do you have installed in your buildroot ?

There is a Bodhi update request to have the new 2.35-18.fc33 update pushed, and it is currently in the testing stage:


Comment 6 Kevin Kofler 2021-01-20 10:36:36 UTC
You fixed only F33, Rawhide/F34 is still broken!

Comment 7 Kevin Kofler 2021-01-20 10:39:21 UTC
The exact version was binutils-2.35.1-23.fc34.x86_64 (binutils-gold-2.35.1-23.fc34.x86_64), which is the latest in Rawhide dist-git. Looks like the fix from https://src.fedoraproject.org/rpms/binutils/c/b6ef4610525f26edea77034d75844389a20aadbc?branch=f33 needs to be applied there too.

Comment 8 Nick Clifton 2021-01-20 13:08:59 UTC
(In reply to Kevin Kofler from comment #6)
> You fixed only F33, Rawhide/F34 is still broken!

Ah - good point.  Unfortunately builds in rawhide appear to be broken at the moment because of a problem with the dwz program.  With a bit of luck it will be fixed soon and I can build a new binutils.

Comment 9 Kevin Kofler 2021-01-20 13:20:46 UTC
Darn, so I cannot fix qt5-qtwebengine because binutils is broken and you cannot fix binutils because dwz is broken, fun!

Comment 10 Jakub Jelinek 2021-01-20 13:24:34 UTC
To be precise, the binutils build did fail because of https://gcc.gnu.org/PR98765 rather than the dwz bug.

Comment 11 Kevin Kofler 2021-01-21 21:47:46 UTC
According to the devel mailing list, gcc and dwz are now fixed in Rawhide, so can we please have a fixed binutils build now?

Comment 12 Nick Clifton 2021-01-22 09:20:38 UTC

Fixed in binutils-2.35.1-24.fc34

Comment 13 Ben Cotton 2021-11-04 16:15:07 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Kevin Kofler 2021-11-05 02:34:21 UTC
AFAICT, this was fixed long ago.

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