Description of problem: A handful of my packages have stopped building successfully in Rawhide. See the z3 package for one example. The cause is this commit: commit 0e07c905671739a43018d9195f7cfc43dfecce93 (origin/f36) Author: Tom Stellard <tstellar> Date: Thu Mar 24 17:26:18 2022 +0000 Add -fno-openmp-implicit-rpath when building with clang This prevents clang from adding RUNPATH for libomp.so to binaries built with -fopenmp. https://fedoraproject.org/wiki/Changes/Broken_RPATH_will_fail_rpmbuild That commit added a tab character in the definition of %__global_compiler_flags. Find %{_legacy_options} in the value. That is followed by a space character, then a tab character. The issue is that some packages break up the flags at spaces, in order to look for specific flags or to add flags of their own. The z3 package, for example, has some python code that does this: def exec_cmd(cmd): if isinstance(cmd, str): cmd = cmd.split(' ') ... The result is one of the commands in the list consists of a single tab character. When that is passed to the compiler, the compiler does not like it at all. Please remove that tab character. Version-Release number of selected component (if applicable): redhat-rpm-config-218-1.fc37.noarch How reproducible: Always Steps to Reproduce: 1. fedpkg clone z3 2. cd z3 3. fedpkg srpm 4. fedpkg mockbuild Actual results: The build fails, complaining that it cannot find a working C++ compiler, even though g++ is installed. Expected results: The build should succeed. Additional info:
https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/187
FEDORA-2022-5626b7ebea has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5626b7ebea
FEDORA-2022-5626b7ebea has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
Hi Miro, thanks for fixing rawhide. Can you also fix F36 as well, please? I can't build WebKitGTK there due to this issue: the tab in CFLAGS is confusing g-ir-scanner.
Sure. I wasn't aware that this regression was backported.
(In reply to Miro Hrončok from comment #5) > Sure. I wasn't aware that this regression was backported. Ping. The 219-1 is broken, but there is no f36 build in koji yet, only 201-1.fc35, which breaks the upgrade path, if I understand the rules properly. Apart of this, I cannot build my packages due to this (gtk-doc is also confused by the args [1]). [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=87538966
(In reply to Milan Crha from comment #6) > only 201-1.fc35, which breaks the upgrade path, if I understand the rules properly. Err, the quoted part is nonsense, I'm sorry, I need to learn read... :-/
f36 PR with the fixes: https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/201
FEDORA-2022-1708a23bac has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1708a23bac
FEDORA-2022-1708a23bac has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-1708a23bac` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1708a23bac See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-1708a23bac has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.