Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1354048 - gcc libgcc subpackage should Provide 'libgcc%{?_isa}'
Summary: gcc libgcc subpackage should Provide 'libgcc%{?_isa}'
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: rawhide
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1352973
TreeView+ depends on / blocked
 
Reported: 2016-07-08 20:24 UTC by Carlos O'Donell
Modified: 2016-07-09 00:46 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-09 00:46:56 UTC


Attachments (Terms of Use)

Description Carlos O'Donell 2016-07-08 20:24:14 UTC
The glibc.i686 package needs libgcc.i686 in order to provide the shared library required for unwinding.

At present glibc.i686 simply 'Requires: libgcc' which is provided by libgcc.x86_64 and this means that 32-bit binaries can mysterious fail in obsccure ways because the unwinder doesn't work and pthread_cancel doesn't work correctly.

The fix is for glibc to Require 'libgcc%{?_isa}' to get the right library.

The problem with this is that libgcc.x86_64 provides both 'libgcc' and 'libgcc(x86_64)', and glibc.i686's Requires on 'libgcc(x86_32)' is apparently resolved by the plain 'libgcc' (architecture neutral?).

Is the correct fix to make the libgcc subpackage provide an explicit 'libgcc%{?_isa}' and stop the automatic generators e.g. use https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering to filter out all libgcc* provides and add them in manually?

Thoughts?

Comment 1 Carlos O'Donell 2016-07-09 00:46:56 UTC
This was a testing mistake on my part. Closing this as 'NOTABUG'.


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