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). �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 depends on 'mpi-default-bin' > ([2]http://packages.debian.org/sid/mpi-default-bin)�which depends on > openmpi-bin for most platforms and mpich2 on others.... But debian/rules > has an explicit dependency on openmpi. �I wonder if we couldn't just say > --mpicc=/usr/bin/mpicc (i.e., unset MPI) to fix the build process on the > other platforms? -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
