Bug 596030 - dosfstools-3.0.9-2.1.el6 should be recompiled with -fno-strict-aliasing
Summary: dosfstools-3.0.9-2.1.el6 should be recompiled with -fno-strict-aliasing
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: dosfstools
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: Radek Bíba
Depends On:
Blocks: 593740
TreeView+ depends on / blocked
Reported: 2010-05-26 07:24 UTC by Jaroslav Škarvada
Modified: 2010-11-10 20:18 UTC (History)
2 users (show)

Fixed In Version: dosfstools-3.0.9-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-11-10 20:18:26 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Jaroslav Škarvada 2010-05-26 07:24:38 UTC
Description of problem:
According to compiler warnings the dosfstools-3.0.9-2.1.el6 uses coding techniques that break strict-aliasing rules, thus it should be recompiled with -fno-strict-aliasing.

Version-Release number of selected component (if applicable):

How reproducible:
Recompile dosfstools-3.0.9-2.1.el6.

Steps to Reproduce:
1. Make scratch build of dosfstools-3.0.9-2.1.el6.
2. Inspects build logs for arches i686, ppc, ppc64, s390.
Actual results:
There are strict-aliasing warnings.

Expected results:
There should be no strict-aliasing warnings.

Comment 1 RHEL Program Management 2010-05-26 07:27:53 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 2 Jaroslav Škarvada 2010-05-26 09:19:24 UTC
Fixed in dosfstools-3.0.9-3.el6.

Comment 5 releng-rhel@redhat.com 2010-11-10 20:18:26 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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