I'm opening this bug because of bug 1217376. tldr: Python saves the compilation/linking flags (used to build Python itself) to a module generated during the build. It then uses these flags as "best" flags to compile C code on the platform - most importantly, it uses them to compile Python C extensions using distutils.
As noted in bug 1217376 comment 3, I think this is right and we should make python-devel depend on redhat-rpm-config. The problem is however that redhat-rpm-config will also draw along some unnecessary deps (for our usecase), like ghc-srpm-macros, perl-srpm-macros etc. - I'd very much like to avoid these for people installing python-devel.
Therefore I'd like to ask you to split /usr/lib/rpm/redhat/redhat-hardened-cc1 and /usr/lib/rpm/redhat/redhat-hardened-ld to a separate subpackage that wouldn't depend on any other package. redhat-rpm-config can depend on this package (as can python-devel), so nothing will change for your use-cases.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.
(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)
More information and reason for this action is here:
Any update on this one?
The foo-srpm-macros packages are really small and should not bring in further dependencies (that'd be bug in them basically). This seems like pointless complication of things, redhat-rpm-config is basically expected to be installed just about everywhere.
That said, having just seen bug 1288717, there appears to be a common theme and maybe it needs more consideration.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 23 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.
Ping? Any updates?
IMO slitting does not make any sense. It is not possible to use complier without linker and vice versa.
Things like using --as-needed in linker should be even part of the default ettings of the liner hardcoded into linker code.
The same is with -fpie.
> I'm opening this bug because of bug 1217376. tldr: Python saves the compilation/linking flags (used to build Python itself) to a module generated during the build.
Such compiler adn linker options should be removed and not propagated as same as for example none of the pkgconfig files shoud be propagating linker and compiler fialgs.
What I've wrote had nothing to do with propagating settings in pkgconfig files.
My comment was purely about default linker options.
If distutil has some problems only this package should be fixed.
distutils needs to be fixed not to hard-code the build flags used at RPM build time because Python developers cannot be expected to have a fully instrumented Fedora build environment installed. This needs to be fixed on the Python side, I'm afraid.
@Florian Ruby suffers similar issues. Would you mind to address my concerns in https://bugzilla.redhat.com/show_bug.cgi?id=1284684#c8 ? Thx.