Description of problem:
Since the hardened by default change, gcc will sometimes fail to compile stuff if redhat-rpm-config isn't installed. This is because it now depends on the redhat-hardened wrappers shipped in redhat-rpm-config.
This problem is so bad that it's documented on developer.fedoraproject.org: https://developer.fedoraproject.org/tech/languages/ruby/gems-installation.html
Please split out the hardening wrappers into their own package and make gcc depend on them.
Version-Release number of selected component (if applicable):
This also affects Fedora 24, Fedora 26, and Rawhide.
This looks like a ruby bug to me. It extracts the build flags from the build environment. As such, it is the responsibility of the ruby package to replicate the build environment (e.g., the rubygems package should depend on redhat-rpm-config).
GCC itself works just fine without redhat-rpm-config.
If it was just ruby, sure. But it also happens with lots of different things.
It's a fairly generic thing, affecting C/C++, Python, and other things that attempt to use GCC.
It's still not a problem with GCC. Those things are passing an option to gcc telling it to use a file that is part of redhat-rpm-config, so those things should depend on redhat-rpm-config.
If I call gcc with -lcurl and haven't installed libcurl-devel it fails to find the file, but that doesn't mean gcc should depend on libcurl.
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
This is definitely still a problem, because I observed this when setting the CI for gsignond.
This is a bug in rubygems because it bakes toolchain compilation flags into RPM packages. It should not do that.