/usr/lib64/cmake/fluidsynth/FluidSynthTargets.cmake creates an imported executable target FluidSynth::fluidsynth that references /usr/bin/fluidsynth. Since /usr/bin/fluidsynth is not installed, cmake fails with: CMake Error at /usr/lib64/cmake/fluidsynth/FluidSynthTargets.cmake:103 (message): The imported target "FluidSynth::fluidsynth" references the file "/usr/bin/fluidsynth" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib64/cmake/fluidsynth/FluidSynthTargets.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib64/cmake/fluidsynth/FluidSynthConfig.cmake:148 (include) CMakeLists.txt:795 (find_package) Reproducible: Always Steps to Reproduce: 1. Create CMakeLists.txt that does `find_package(FluidSynth CONFIG REQUIRED)` 2. Configure the project Actual Results: Error with: CMake Error at /usr/lib64/cmake/fluidsynth/FluidSynthTargets.cmake:103 (message): The imported target "FluidSynth::fluidsynth" references the file "/usr/bin/fluidsynth" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib64/cmake/fluidsynth/FluidSynthTargets.cmake" but not all the files it references. Expected Results: No error. /usr/bin/fluidsynth is installed automatically when installing fluidsynth-devel An alternative solution is to split fluidsynth's target config file in multiple ones, as done by e.g. SDL. Installing the fluidsynth package also fixes the issue. But I believe this bug report is useful as it points at a missing dependency.
FEDORA-2023-a21634e279 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a21634e279
FEDORA-2023-3600fbe804 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-3600fbe804
FEDORA-EPEL-2023-3f6171b6f3 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-3f6171b6f3
FEDORA-2023-a21634e279 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-a21634e279` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-a21634e279 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2023-3f6171b6f3 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-3f6171b6f3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-3600fbe804 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-3600fbe804` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3600fbe804 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-a21634e279 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-3600fbe804 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2023-3f6171b6f3 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.