Bug 2385368

Created attachment 2101019 [details]
build.log

Created attachment 2101020 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Created attachment 2101021 [details]
state.log

Ran into the failure to build stock openocd on Fedora myself while trying to patch it to work around an issue with a particular piece of hardware (truly a rabbit hole within a rabbit hole).

As far as I can tell this build failure is caused by an upstream bug. The sdcc toolchain used to compile some firmware as part of the openocd build process has been updated upstream including a breaking change to the acceptable syntax for the `__interrupt` keyword for marking ISRs and that new version has been brought into Fedora. Since upstream provides a prebuilt binary (but this is unacceptable to us in Fedora) for that firmware, I imagine they don't try rebuild it very often upstream or if they do, they are not using the more up to date version of sdcc that we have in Fedora. I filed a change request in upstream gerrit https://review.openocd.org/c/openocd/+/9514 and if it lands it should be possible to update the version of openocd to one that contains the commit, and/or add that single patch to the dist-git to fix the issue.

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

FEDORA-2026-764602fa69 (openocd-0.12.0-4.gitcb52502.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-764602fa69

FEDORA-2026-764602fa69 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-764602fa69`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-764602fa69

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Hi Peter—

Just wondering if you considered taking my proposed patch as a downstream fix instead of removing ulink to fix the build. Probably not a tremendous amount of folks are using the ulink transport, but removing it is a slight feature regression when fixing the code is quite easy as demonstrated by my proposed patch. If you aren't interested in it, then you might want to at least remove sdcc as a build requires since iirc it was only used to compile the ulink firmware which you are disabling. 

Best—Charlie

I am not aware of a downstream patch, please provide a linl, I only took over maintainership when it was orphaned recently.

There's another firmware (ANGIE) that's built with sdcc and that's why i left it there.

Hmm, I saw angie when I did a quick `git grep sdcc` in the tree, but I didn't think angie was enabled in the Fedora build (though I did not try building without sdcc to confirm). I shared my patch in comment 4 on this issue, but also here you go: https://review.openocd.org/c/openocd/+/9514. I haven't received any traction on their gerrit and had meant to follow up by asking on the mailing list, but it sorta fell off my radar until I saw your updates on this issue.

FEDORA-2026-764602fa69 (openocd-0.12.0-4.gitcb52502.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.