Bug#673911: Build-Depends: mpi-default-bin vs. /usr/bin/mpicc.openmpi

2012-06-05 Thread Yaroslav Halchenko
BTW -- that was a good hutch but now I guess I would need to look into what causes cmdline options incompatibilities (that is on s390 box): testLastUsedCode (test_environ.TestWorldAttrs) ... ok testUniverseSize (test_environ.TestWorldAttrs) ... [mpiexec@zelenka] match_arg (./utils/args/args.c:122

Bug#673911: Build-Depends: mpi-default-bin vs. /usr/bin/mpicc.openmpi

2012-06-04 Thread Yaroslav Halchenko
good call -- just for the sake of testing I guess I should better first test it on e.g. s390 -- will request access to it On Mon, 04 Jun 2012, Bradley M. Froehle wrote: >The buildd status page for mpi4py shows some failed builds >([1]https://buildd.debian.org/status/package.php?p=mpi4py).

Bug#673911: Build-Depends: mpi-default-bin vs. /usr/bin/mpicc.openmpi

2012-06-04 Thread Bradley M. Froehle
The buildd status page for mpi4py shows some failed builds ( https://buildd.debian.org/status/package.php?p=mpi4py). While none of these are new (i.e., they also failed for 1.2.2-3), I think many of these are caused by a mismatch between the control & rules. In particular, the package build depen