FEDORA-2022-7a51ade8e5 — unspecified update for binutils

obsolete

binutils-2.37-32.fc36

FEDORA-2022-7a51ade8e5 created by nickc 2 years ago for Fedora 36

Fix building the binutils for Risc64 and AArch64

Fix bug in binutils.spec file that was causing the wrong linker flags to be used.
Change the ld man page so that it says that --enable-new-dtags is the default. (#2090818)

Stop readelf and objdump from unnecessarily following links.

Add support for generating static PIE binaries for the s390x

This update has been submitted for testing by nickc.

2 years ago

This update's test gating status has been changed to 'waiting'.

2 years ago

This update has obsoleted binutils-2.37-31.fc36, and has inherited its bugs and notes.

2 years ago

This update's test gating status has been changed to 'passed'.

2 years ago

This update's test gating status has been changed to 'failed'.

2 years ago

This update has been pushed to testing.

2 years ago

bojan commented & provided feedback 2 years ago

karma

Works.

andilinux commented & provided feedback 2 years ago

karma

works

andilinux commented & provided feedback 2 years ago

karma

works

geraldosimiao provided feedback 2 years ago

karma

filiperosset commented & provided feedback 2 years ago

karma

no regressions noted

This update has been obsoleted by binutils-2.37-34.fc36.

2 years ago

Please login to add feedback.

Metadata

Type

unspecified

Karma

Signed

Content Type

RPM

Test Gating

failed

Autopush Settings

Unstable by Karma

-3

Stable by Karma

Stable by Time

14 days

Thresholds

Minimum Karma

Minimum Testing

14 days

Dates

submitted

2 years ago

in testing

2 years ago

Builds

binutils-2.37-32.fc36

BZ#2086863 readelf is trying to reach debuginfod remote server?

binutils-2.37-32.fc36

Automated Test Results

For help debugging failed Fedora CI tests (fedora-ci.*), contact the Fedora CI team.
For help debugging failed Fedora CoreOS tests (coreos.*), contact the Fedora CoreOS team.
For help debugging failed openQA tests (update.*), contact the Fedora Quality team, who will usually investigate and diagnose all failures within 24 hours.

failed