Bug 967524
Summary: | Inconsistent prefix | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Miroslav Rezanina <mrezanin> |
Component: | mingw-filesystem | Assignee: | Kai Tietz <ktietz> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.0 | CC: | mnewsome, mrezanin |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-05-28 05:29:28 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
Miroslav Rezanina
2013-05-27 10:54:35 UTC
No, there are two prefixes. One is mingw32- for 32.bit binary package, and the other is mingw64- for 64-bit one. The host triplet used for cross-compilers are x86_64-w64-mingw32... for 64-bit, and i686-w64-mingw32... for 32-bit. The source packages are using just mingw-.... prefix, as they are target-indepent. I think this bug is invalid. Ok, thanks for explaining... |