RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 768213 - mingw32-gcc.i686 does not exist
Summary: mingw32-gcc.i686 does not exist
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mingw32-gcc
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Kai Tietz
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-16 03:37 UTC by Johnny Hughes
Modified: 2012-10-09 09:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-09 09:46:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Johnny Hughes 2011-12-16 03:37:41 UTC
Description of problem:  There are mingw32*.noarch.rpm packages in the i386 arch for RHEL 6.2.  All these packages require things that would be in mingw32-gcc.i686 ... however there is no mingw32-gcc.i686 RPM.

package: mingw32-boost-1.41.0-3.el6.noarch
  unresolved deps: 
     mingw32(libgcc_s_sjlj-1.dll)
package: mingw32-gettext-0.17-12.el6.5.noarch
  unresolved deps: 
     mingw32(libgcc_s_sjlj-1.dll)
     mingw32(libgomp-1.dll)
package: mingw32-pcre-8.10-2.el6.5.noarch
  unresolved deps: 
     mingw32(libgcc_s_sjlj-1.dll)
package: mingw32-pthreads-2.8.0-10.el6.7.noarch
  unresolved deps: 
     mingw32(libgcc_s_sjlj-1.dll)
package: mingw32-qpid-cpp-0.10-1.el6.noarch
  unresolved deps: 
     mingw32(libgcc_s_sjlj-1.dll)


This shows mingw32*.noarch.rpm files as active on the i386 arches:

http://rhn.redhat.com/errata/RHEA-2011-0671.html

Comment 2 Kai Tietz 2011-12-16 08:32:09 UTC
Hmm, we had this issue already.  As defined for mingw-* packages, the binary-packages are only available for x86_64 host-architecture.  So those DLL files mentioned here are part of the mingw-gcc package, which isn't present for i?86 architecture.

As far as I remember was dgregor handling this for RHEL 6.2.  Not sure, if he missed those packages, or if the issue isn't resolvable.

Comment 3 Kai Tietz 2012-01-17 17:22:48 UTC
Well, that those DLL file-packages are noarch seems to me the right thing.
As long as x86_64 shall architecture shall be the only architecture for mingw-packages, I don't see how to resolve this issue.

Comment 5 Matt Newsome 2012-10-09 09:46:58 UTC
Thanks for letting us know. mingw32-gcc is provided via the optional channel for x86_64 only. Additionally, as per the scope of coverage:

https://access.redhat.com/support/offerings/production/soc.html

the Optional channel is not supported. We can't unfortunately resolve this issue.


Note You need to log in before you can comment on or make changes to this bug.