Re: PetSc
In Thu, 11 Jan 2001 12:14:02 -0500 Adam C Powell IV <hazelsct@mit.edu> cum veritate scripsit :
> Right. The other problem is that mpirun takes different arguments for
> mpich and lam, and
> PETSc comes with a compatibility wrapper script "mpirun.lam" which takes
> arguments in mpich
> format.
Hmmm.. that's very interesting.
> Oh- and mpich doesn't have shared libs, so when you link -mpi
> and
> /etc/alternatives points to mpich, there are dangling symlinks for
> libmpi.so. :-(
Actually it is possible to build shared library for mpich, and
I tried it. It was not very exciting.
Hmmm.. I didn't know there was a dangling symlink.
Okay... please file a bug.
Ah, yes. This is a nightmare, trying to compile against mpich AND lam.
regards,
junichi
--
University: ti0113@mail4.doshisha.ac.jp Netfort: dancer@netfort.gr.jp
dancer, a.k.a. Junichi Uekawa http://www.netfort.gr.jp/~dancer
Dept. of Knowledge Engineering and Computer Science, Doshisha University.
... Long Live Free Software, LIBERTAS OMNI VINCIT.
Reply to:
- Follow-Ups:
- Re: PetSc
- From: Mark Brown <broonie@sirena.org.uk>
- Re: PetSc
- From: Camm Maguire <camm@enhanced.com>
- References:
- PetSc
- From: "Eray Ozkural \(exa\)" <erayo@cs.bilkent.edu.tr>
- Re: PetSc
- From: Adam C Powell IV <hazelsct@mit.edu>
- Re: PetSc
- From: Junichi Uekawa <dancer@netfort.gr.jp>
- Re: PetSc
- From: Brian Mays <brian@debian.org>
- Re: PetSc
- From: Junichi Uekawa <dancer@netfort.gr.jp>
- Re: PetSc
- From: Adam C Powell IV <hazelsct@mit.edu>