[openfabrics-ewg] RE: Open-MPI issue on PPC64 platform

[Jeff Squyres (jsquyres)]

We used to do things like this (automatically insert flags into wrapper
compilers), but got quite legitimate complaints from users who *didn't*
want that to happen for whatever reason.

Indeed, it seems like a never-ending list (and maintenance-intensive)
chunk of code if you start trying to figure out what flags in CFLAGS,
CPPFLAGS, CXXFLAGS, CXXCPPFLAGs, F77FLAGS, FCFLAGS, LDFLAGS, and LIBS
are "special" and worthy of being put into the wrapper compilers
(because it is not appropriate to just dump the contents of all of those
into each of the respective wrappers).  Given that building is a
relatively rare case, it seemed a reasonable software engineering
compromise to simply make the builder specify exactly which flags they
want in the wrapper compilers.


> -----Original Message-----
> From: Pavel Shamis (Pasha) [mailto:pasha at mellanox.co.il] 
> Sent: Monday, May 22, 2006 7:36 AM
> To: Jeff Squyres (jsquyres)
> Cc: openfabrics-ewg at openib.org
> Subject: Re: [openfabrics-ewg] RE: Open-MPI issue on PPC64 platform
> 
> Ok, Vlad will add these flags to OFED build scripts.
> 
> But I think that for this platform the "-m64" flag should be added 
> automatically by open-mpi configure script, because without this flag 
> ,the installation (mpicc and other wrappers) will not be 
> functional from 
> user point of view.
> 
> Regards,
> Pasha.
> 
> Jeff Squyres (jsquyres) wrote:
> > If you need additional flags to also be passed through the wrapper
> > compilers, you need to use the following flags to Open 
> MPI's configure:
> > 
> >   --with-wrapper-cflags   Extra flags to add to CFLAGS when 
> using mpicc
> >   --with-wrapper-cxxflags Extra flags to add to CXXFLAGS when using
> > mpic++/mpiCC
> >   --with-wrapper-fflags   Extra flags to add to FFLAGS when 
> using mpif77
> >   --with-wrapper-fcflags  Extra flags to add to FCFLAGS when using
> > mpif90
> > 
> > Specifically, Open MPI does not automatically pass all 
> flags supplied by
> > CFLAGS, CXXFLAGS (etc.) specified by configure to the 
> wrapper compiler
> > because there are many cases where you want Open MPI built 
> with one set
> > of flags and your user app built with another (e.g., build 
> an optimized
> > MPI but build your application with -g).  So if you specify:
> > 
> >     ./configure --with-wrapper-cflags=-m64 
> --with-wrapper-cxxflags=-m64
> > ...etc.
> > 
> > Then the wrapper flags will include -m64 and the user codes 
> won't need
> > to include that on their compile/link command lines.
> > 
> > 
> >> -----Original Message-----
> >> From: Pavel Shamis (Pasha) [mailto:pasha at mellanox.co.il] 
> >> Sent: Sunday, May 21, 2006 1:02 PM
> >> To: Jeff Squyres (jsquyres)
> >> Cc: openfabrics-ewg-bounces at openib.org; vlad at mellanox.co.il
> >> Subject: Open-MPI issue on PPC64 platform
> >>
> >> Hi Jeff,
> >> We figured out the following issue with Open-Mpi installation 
> >> on Fedora 
> >> Core 4 PPC64 platform:
> >> open-mpi passes the installation without problem and it 
> >> builds 64bit mpi 
> >> library. But if we try build some benchmarks (in our case mpitest 
> >> package) the mpicc fails on linkage. On Fedora C4 PPC64 by 
> >> default gcc 
> >> use -m32 (!?) flag so in order to build 64bit binary you 
> >> should add -m64 
> >> flag and mpicc doesn't add it.
> >>
> >> Regards,
> >> Pasha
> >>
> > _______________________________________________
> > openfabrics-ewg mailing list
> > openfabrics-ewg at openib.org
> > http://openib.org/mailman/listinfo/openfabrics-ewg
> > 
>