it seems that 1. we lost mpi.cfg
neurodebian@head2:~/deb/builds/mpi4py/1.2.2-4$ dpkg -c python-mpi4py_1.2.2-4_amd64.deb | grep mpi.cfg neurodebian@head2:~/deb/builds/mpi4py/1.2.2-4$ cd ../1.2.2-3/ neurodebian@head2:~/deb/builds/mpi4py/1.2.2-3$ dpkg -c python-mpi4py_1.2.2-[34]_amd64.deb | grep mpi.cfg -rw-r--r-- root/root 121 2012-05-22 12:24 ./usr/share/pyshared/mpi4py/mpi.cfg 2. I have forgotten to add assurance that those loops fail if any iteration fails (committed now), so we got such failures masked: building 'python3.2-mpi' executable /usr/bin/mpicc -fPIC -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -I/usr/include/python3.2mu -c src/python.c -o build/temp.linux-x86_64-3.2/src/python.o /usr/bin/mpicc -Wl,-export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions build/temp.linux-x86_64-3.2/src/python.o -L/usr/lib/python3.2/config-3.2mu -lpython3.2 -o build/exe.linux-x86_64-3.2/python3.2-mpi -Wl,-z,relro -lpthread -ldl -lutil -lssl -lcrypto -lssl -lcrypto -lffi -L/usr/lib -lz -lexpat -lm /usr/bin/ld: cannot find -lffi collect2: error: ld returned 1 exit status warning: build_exe: building extension "python3.2-mpi" failed warning: build_exe: command '/usr/bin/mpicc' failed with exit status 1 do you have a clue why ffi become present while building for 3.x? I just wonder if we should complain elsewhere or just add it as build-depends for now... On Mon, 21 May 2012, Yaroslav Halchenko wrote: > ok -- let's upload this one, see it migrate (or not) to testing and then > 1.3! > thanks for all the help! -- 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
