Bug 596636

Summary: OpenLDAP should be compiled with -fno-strict-aliasing
Product: Red Hat Enterprise Linux 6 Reporter: Jan Zeleny <jzeleny>
Component: openldapAssignee: Jan Zeleny <jzeleny>
Status: CLOSED DUPLICATE QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: jplans, ovasik
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-27 10:55:27 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: 596193    

Description Jan Zeleny 2010-05-27 08:15:50 UTC 
According to RPMdiff, compilation contains some warnings which should be dealt with:

422  ../dist/../btree/bt_delete.c: In function '__bam_ditem_openldap_slapd_46':
   423  ../dist/../btree/bt_delete.c:88: warning: dereferencing type-punned pointer will break strict-aliasing rules
   424  ../dist/../btree/bt_delete.c: In function '__bam_dpages_openldap_slapd_46':
   425  ../dist/../btree/bt_delete.c:404: warning: dereferencing type-punned pointer will break strict-aliasing rules
   434  ../dist/../btree/bt_put.c: In function '__bam_irep_openldap_slapd_46':
   435  ../dist/../btree/bt_put.c:828: warning: dereferencing type-punned pointer will break strict-aliasing rules
   436  ../dist/../btree/bt_rec.c: In function '__bam_pgno_recover_openldap_slapd_46':
   437  ../dist/../btree/bt_rec.c:1860: warning: dereferencing type-punned pointer will break strict-aliasing rules
   450  ../dist/../btree/bt_stat.c: In function '__bam_traverse_openldap_slapd_46':
   451  ../dist/../btree/bt_stat.c:604: warning: dereferencing type-punned pointer will break strict-aliasing rules

This can be fixed by adding -fno-strict-aliasing to compilation rules.
Comment 1 Jan Zeleny 2010-05-27 10:55:27 UTC 
After consultation this bug will be taken care of in bug 596193

*** This bug has been marked as a duplicate of bug 596193 ***