[Pvfs2-developers] Re: EVP warning and statlite compilation
Robert Latham
robl at mcs.anl.gov
Thu Oct 5 16:19:09 EDT 2006
On Thu, Sep 14, 2006 at 05:47:53PM -0500, Sam Lang wrote:
> It would be nice if instead of --with-file-system=pvfs2, there were a
> --with-pvfs2=<path>.
Done! Checked it into MPICH2 cvs yesterday (took me a while to find
this mail)
> That way, we wouldn't have to set CFLAGS/LDFLAGS/LIBS before configure,
> _and_ we could tell mpich2 exactly what include paths, lib paths, and
> libs to use via pvfs2-config (which, btw, doesn't seem to have the
> execute flag set on it when it gets built).
It's installed with execute set. Does it need to be +x in the tree
too?
> I guess this is more of a mpich2 issue than pvfs2, but it seems like
> pushing in that direction is a cleaner solution, i.e. who knows what
> libs we might by linking with in the future, when the problem is just
> going to pop up all over again.
Totally agree. I'm quite happy to have ROMIO using pvfs2-config.
Thanks for the kick in the pants to get that working at last.
The mechanism I used to feed libraries up to MPICH2 is, well, MPICH2
specific. The old approach of setting CFLAGS/LDFLAGS/LIBS will still
work, so we're still backwards compatible and compatible with other
MPI implementations.
==rob
--
Rob Latham
Mathematics and Computer Science Division A215 0178 EA2D B059 8CDF
Argonne National Labs, IL USA B29D F333 664A 4280 315B
More information about the Pvfs2-developers
mailing list