Bug 355551
| Summary: | rpmrc provides obsolete default switches | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Devrim GUNDUZ <devrim> |
| Component: | rpm | Assignee: | Panu Matilainen <pmatilai> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.0 | CC: | devrim, tgl |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-01-20 20:48:44 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 454887 | ||
| Bug Blocks: | |||
|
Description
Devrim GUNDUZ
2007-10-28 01:07:20 UTC
You need to have redhat-rpm-config installed when building packages for RHEL/Fedora, otherwise a number of things will be wrong. Rpm upstream configuration such as optflags are in reality totally irrelevant as it's not rpm's business to know or dictate which version of some compiler is used to build something. redhat-rpm-config defines the distro-level policy/configuration for building packages for use in RHEL/Fedora, however nothing says you can't define and use your own configuration for other purposes. So rpm-build requiring redhat-rpm-config would be wrong too. This has been "fixed" in rpm upstream (and thus Fedora >= 7) by defaulting to newer gcc flags, but actually the real fix would be to remove any such flags from the upstream configuration, for the reasons stated above. This situation doesn't seem very satisfactory to me. It's agreed by all that you *must* have redhat-rpm- config installed to get sane build results on Red Hat platforms. Shouldn't we have some mechanism better than "expect the end user to get it right with no prompting" to enforce that? I would normally expect the package require infrastructure to do this, but if neither rpm-build nor the individual SRPMs should Require: it (and I do see your point about why they shouldn't), what then? Perhaps we should re-file this bug against the distribution, that is that redhat-rpm-build should be forcibly installed on every Red Hat configuration? If you don't like that, then what component *should* take responsibility for getting this right? I do agree it's hardly an optimal situation. "Development Tools" group contains redhat-rpm-config, I guess that's how it typically gets installed (otherwise we'd have many many more dupes of this :), but that doesn't help somebody who does a base install first and then adds individual packages afterwards. The RPM rebase in 5.3 includes a fix for this issue. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0079.html |