Bug 605200

Summary: makebootfat-1.4-9.1.el6 should be recompiled with -fno-strict-aliasing
Product: Red Hat Enterprise Linux 6 Reporter: Jaroslav Škarvada <jskarvad>
Component: makebootfatAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED CURRENTRELEASE QA Contact: Miroslav Vadkerti <mvadkert>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: asersen, jskarvad, mvadkert, rvokal
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: makebootfat-1.4-10.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-10 21:08:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 593740    

Description Jaroslav Škarvada 2010-06-17 12:18:53 UTC
Description of problem:
According to compiler warnings the makebootfat-1.4-9.1.el6 uses coding techniques
that break strict-aliasing rules, thus it should be recompiled with

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

How reproducible:
Recompile makebootfat-1.4-9.1.el6.

Steps to Reproduce:
1. Make scratch build of makebootfat-1.4-9.1.el6.
2. Inspects build logs.

Actual results:
There are strict-aliasing warnings.

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

Comment 1 RHEL Product and Program Management 2010-06-17 12:33:16 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 Miroslav Vadkerti 2010-06-18 13:56:44 UTC
qack .. will be tested in next rpmdiff run

Comment 3 Jaroslav Škarvada 2010-06-21 07:26:53 UTC
Fixed in makebootfat-1.4-10.el6.

Comment 5 releng-rhel@redhat.com 2010-11-10 21:08:52 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.