Hide Forgot
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!
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 4. GNU_PROPERTY_X86_FEATURE_2_NEEDED, GNU_PROPERTY_X86_FEATURE_2_USED and GNU_PROPERTY_X86_FEATURE_2_XXX bits. GNU_PROPERTY_X86_FEATURE_1_AND is unchanged. GNU_PROPERTY_X86_ISA_1_USED 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 GNU_PROPERTY_X86_COMPAT_ISA_1_XXX and GNU_PROPERTY_X86_COMPAT_2_ISA_1_XXX.
This should be fixed in binutils-2.35-18.fc33.
I'm also getting this on Rawhide and it breaks qt5-qtwebengine builds.
This is hindering my attempts to fix a QtWebEngine issue, see: https://bugzilla.redhat.com/show_bug.cgi?id=1904652#c9
(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: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d41be3cf52
You fixed only F33, Rawhide/F34 is still broken!
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.
(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.
Darn, so I cannot fix qt5-qtwebengine because binutils is broken and you cannot fix binutils because dwz is broken, fun!
To be precise, the binutils build did fail because of https://gcc.gnu.org/PR98765 rather than the dwz bug.
According to the devel mailing list, gcc and dwz are now fixed in Rawhide, so can we please have a fixed binutils build now?
Done! Fixed in binutils-2.35.1-24.fc34
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.
AFAICT, this was fixed long ago.