Bug 596030

Summary:	dosfstools-3.0.9-2.1.el6 should be recompiled with -fno-strict-aliasing
Product:	Red Hat Enterprise Linux 6	Reporter:	Jaroslav Škarvada <jskarvad>
Component:	dosfstools	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Radek Bíba <rbiba>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	jskarvad, rvokal
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	dosfstools-3.0.9-3.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-10 20:18:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	593740

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):
dosfstools-3.0.9-2.1.el6

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
inclusion.

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.