I've set up an mpi build of gerris (gerris for non-mpi, gerris-mpi for the mpi build). I used debhelper's new dh command and the override mechanism to get the two builds side by side.
The build succeeded on my amd64 system, of course, and in fact has succeeded on the 5 different architectures where mpi-default-dev is open-mpi, see https://buildd.debian.org/build.cgi?pkg=gerris. On the other architectures however, where mpi-default-dev is lam, the mpi build fails at: /bin/sh ../libtool --silent --tag=CC --mode=compile mpicc -DHAVE_CONFIG_H -I. -I../../../src -I.. -I../../.. -I/usr/include -DG_LOG_DOMAIN=\"Gfs\" -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include -DGFS_MODULES_DIR= \"/usr/lib/gerris\" -DFTT_2D=1 -g -O2 -Wall -Werror-implicit-function-declaration -Wmissing-prototypes -Wmissing-declarations -pipe -c -o libgfs2D_la-utils.lo `test -f 'utils.c' || echo '../../../src/'`utils.c ../../../src/utils.c: In function 'compile': ../../../src/utils.c:484: error: expected ',' or ';' before 'MODULES_FLAGS' mpicc: No such file or directory make[5]: *** [libgfs2D_la-utils.lo] Error 1 I don't understand why this error is popping up at this point. I presume the ',' or ';' error is related to mpicc not being found. But the same compile line with mpicc worked fine in the same build for a dozen other source files before it got to utils.c. Those with a specific interest in mpi or lam on the less common architectures, this might be a good bug for you! The failing architectures are alpha armel hppa mips mipsel s390 sparc They have in common that mpi-default-dev is lam4. The successful ones are i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc and amd64. mpi-default-dev is openmpi on these. I'd welcome any help with this. Drew -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
