[mpich-discuss] Adding libraries to the mpicc wrapper

Matthieu Dorier matthieu.dorier at irisa.fr
Wed Jan 15 10:36:37 CST 2014


Thanks Rob!

Matthieu Dorier 
PhD student at ENS Rennes 
http://people.irisa.fr/Matthieu.Dorier 

----- Mail original -----
> De: "Rob Latham" <robl at mcs.anl.gov>
> À: discuss at mpich.org
> Envoyé: Mercredi 15 Janvier 2014 17:15:49
> Objet: Re: [mpich-discuss] Adding libraries to the mpicc wrapper
> 
> 
> 
> On 01/15/2014 08:55 AM, Matthieu Dorier wrote:
> > Hello,
> >
> > I have written an ADIO backend that depends on a library. So far to
> > make
> > the use of the library transparent when compiling a program, I
> > added the
> > library at line 226 of the mpicc wrapper (mpilibs=" -lmpich
> > -lmylibrary"). I'd like to know if there is a "cleaner" way of
> > adding
> > it: mpicc being generated from a template, there should be a way to
> > simply set a variable somewhere for that, shouldn't it? How is it
> > done
> > for other ADIO backends?
> 
> Hey Mattieu!
> 
> for old pvfs and lustre, add to LDFLAGS and LIBS when configuring
> mpich
> (and in turn, romio)
> 
> for pvfs2, ROMIO's configure looked for and used pvfs2-config to add
> the
> appropriate libraries and headers.  ROMIO would then add those to
> 'src/mpi/romio/localdefs' so the needed libraries would propagate up
> to
> the mpicc wrapper.
> 
> ==rob
> 
> 
> --
> Rob Latham
> Mathematics and Computer Science Division
> Argonne National Lab, IL USA
> _______________________________________________
> discuss mailing list     discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss
> 



More information about the discuss mailing list