Bug 713685

Summary: ARM doesn't support -m32 or -m64
Product: [Fedora] Fedora Reporter: Peter Robinson <pbrobinson>
Component: mpich2Assignee: Deji Akingunola <dakingun>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dakingun
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-04 23:13:52 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: 245418    

Description Peter Robinson 2011-06-16 09:03:42 UTC 
mpich2 doesn't support the -m32 or -m64 gcc options so for %{arm} we need to either clear the setting or set it to something more appropriate for the platform so that it will compile.

http://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html
Comment 1 Dennis Gilmore 2011-06-16 15:06:04 UTC 
the standard fedora cflags set -m32 and -m64 as appropriate, we should just patch out of mpich2 anything that tries to be too smart. and just rely on whats set by us.
Comment 2 Deji Akingunola 2011-06-16 15:48:43 UTC 
(In reply to comment #1)
> the standard fedora cflags set -m32 and -m64 as appropriate, we should just
> patch out of mpich2 anything that tries to be too smart. and just rely on whats
> set by us.

One need to look closely at the spec and have some understanding of how mpich2 behaves to understand what the 'm_option' macros (that sets the -m32/-m64) does. That macro is NOT for setting the compiler flag in building the mpich2 library, but for specifying the basic flag the built mpi compiler should use (once installed).
Comment 3 Deji Akingunola 2011-07-04 23:13:52 UTC 
Fixed.