Fedora Account System
Red Hat Associate
Red Hat Customer
sdcc-sdcc sets the path to include /usr/libexec/sdcc in the PATH, but it doesn't include the /usr/libexec/sdcc/x86_64-redhat-linux-gnu/12.1.0 directory where cc1 resides, so it fails with "sdcpp: fatal error: cannot execute 'cc1': execvp: No such file or directory" Editing the sdcc-sdcc script to add this extra directory to the PATH fixes the problem. Reproducible: Always Steps to Reproduce: 1. sdcc-sdcc -mmcs51 -c main.c with some random main.c Actual Results: sdcpp: fatal error: cannot execute 'cc1': execvp: No such file or directory Expected Results: It should call cc1 from the subdirectory Changing line 2 of the sdcc-sdcc script to PATH=/usr/libexec/sdcc:/usr/libexec/sdcc/x86_64-redhat-linux-gnu/12.1.0/:$PATH fixes the problem on my system, though I guess the exact subdirectory will depend on the system.
This bug is still reproducible in Fedora 42 with SDCC 4.4.0-2.fc42. Is there any new update?
FEDORA-2025-a989aece56 (sdcc-4.4.0-3.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-a989aece56
FEDORA-2025-a989aece56 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-a989aece56` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-a989aece56 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
This fixes the bug for me. Thanks.
FEDORA-2025-a989aece56 (sdcc-4.4.0-3.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.