Follow-up: Fedora 43 RISC-V status

Project Discussion
1

This is a follow-up to the previous update[1]. Some of you might be wondering about F43 RISC-V release.

We’re saddled with a complex bug[2][3][4] related to ‘debugedit’ (a set of tools and scripts for creating, managing, and editing debug information) that is affecting some 1000 odd packages. Almost 95% of F43 has been ready for a while, the rest is affected by this annoying bug.

We’ve been actively debugging it for several weeks by working with relevant upstream maintainers. We’re trying to get this resolved before the F44 mass-rebuild starts.

We’ll keep you posted as we know more.

Regards,

Fedora RISC-V community

[1] https://discussion.fedoraproject.org/t/interim-update-on-fedora-43-risc-v-images/170955

[2] https://forge.fedoraproject.org/riscv/planning/issues/1 — Some package builds fail because ‘debugedit’ cannot read debug sections

[3] https://sourceware.org/bugzilla/show_bug.cgi?id=33723 — Debug info corruption due to relocations past end of .debug_line_str

[4] https://sourceware.org/bugzilla/show_bug.cgi?id=33789 — debugedit corrupts RISC-V object files

1 Like
2

A quick update:

Good news: Mark Wiielaard submitted a patch[1] to ‘debugedit’ upstream. And David Abdurachmanov made a Fedora build[2] for ‘debugedit’ with it.

We’re now rebuilding the failing packages.

More updates coming soon.

[1] https://https://inbox.sourceware.org/debugedit/20260121123342.137521-1-mark@klomp.org/
[2] https://https://sourceware.org/bugzilla/show_bug.cgi?id=33789