Bug 977553
Summary: | broken symlinks in GCC packages | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Harald Reindl <h.reindl> |
Component: | gcc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | jakub, law |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-25 05:44:15 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Harald Reindl
2013-06-24 21:54:27 UTC
This is intentional, so that the package supports both -m64 and -m32 compilation, if you install the 32-bit rpms things work automatically, but that the 32-bit packages aren't required. intentionally broken? why do not only the 32bit rpms create these symlinks? yes, ifarch-constrcuts in SPEC-file exists Why do you use a word broken? I don't see anything broken on the current state. And, the 32-bit packages shouldn't be putting symlinks into the paths they shouldn't own (x86_64 specific paths). because the symlinks are broken? this is how a symlink pointing to nowhere is called! sorry, but i do *really* not understand why a 100% clean x86_64 setup is cluttered with symlinks pointing to nowhere somebody *could* find useable if he has 32bit packages installed i killed them multiple times because and thought they where from non-perfect dist-upgrades but after find them again i looked which package clutters my machine |