Hi Ondrej!
Am Mittwoch, den 12.12.2007, 12:50 +0100 schrieb Ondrej Certik:
libmesh depends on openmpi, it build in pbuilder, however it fails on
buildbots:
http://buildd.debian.org/fetch.cgi?pkg=libmesh;ver=0.6.1.dfsg-1;arch=amd64;stamp=1197413726
I suspect the problem is with the mpicc missing when you had lam/mpich
before, removed that
and installed openmpi over it.
I reported the bug about it, but you decided it's not a bug, that I can clean
the environment myself (I did and it worked). But I think it's a bug, becase
obviously I cannot clean the environment on buildbots by hand.
Something needs to be done about this.
Any ideas?
As far as I can tell, the compilers should work fine as long if you have
the libopenmpi-dev package installed. Though, we're experiencing some
problems with multiple MPI implementations installed, see #452047 and
#451993. It sounds like it affects you as well but I'm not quite sure
from your report. Do you build against several MPI alternatives?
In case you build against several MPI implementations, you should pass
MPICC=/usr/bin/mpicc.openmpi to the configure script. Autotools should
support that, and you should be specific about what compiler you want.
If you just build against a single MPI implementation, mpicc should
exist and work. I can't reprocuce the behavior that they are not
created.
The problem mentioned in the bugs above results in broken alternatives
for linking, so you should get trouble way after configuring. We're
going to upload a package that should fix a part of the problem but the
real problem is that we're experiencing a bug in update-alternatives
which does not create the links in a reasonable and reliable way, so
until that's fixed, I'm not sure if you'll be able to get things to
work.
Best regards
Manuel
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
