Bug#602660: petsc: FTBFS on armel
Adam C Powell IV
hazelsct at debian.org
Mon Nov 8 14:44:32 UTC 2010
Hi Hector,
On Mon, 2010-11-08 at 14:18 +0000, Hector Oron wrote:
> 2010/11/7 Adam C Powell IV <hazelsct at debian.org>:
>
> > Hi, unfortunately the build log for this configure process doesn't
> > provide just about any needed info. Is there a way to get the
> > configure.log file to determine what went wrong?
>
> Could you try to log into abel.debian.org (armel porterbox) and test a
> build there?
>
> I did so, but I am getting:
> [...]
> Using MPI implementation lam in directory /usr/lib/lam
> cp -fp /usr/share/automake-1.11/config.* config/configarch/
> cp -fp /usr/share/automake-1.11/config.* config/BuildSystem/config/packages/
> if [ ! -f TAGS.backup ]; then cp -a TAGS TAGS.backup; fi
> PETSC_DIR=/home/zumbi/petsc-3.1.dfsg PETSC_ARCH=linux-gnueabi-c-debug \
> ./config/configure.py --with-debugging=1 \
> --useThreads 0 --with-clanguage=C++ --with-c-support \
> --with-fortran-interfaces=1 \
> --with-mpi-dir=/usr/lib/lam \
> --with-blas-lib=-lblas --with-lapack-lib=-llapack \
> --with-blacs=1 --with-blacs-include=/usr/include \
> --with-blacs-lib=[/usr/lib/libblacs-lam.so,/usr/lib/libblacsCinit-lam.so]
> \
> --with-scalapack=1 --with-scalapack-include=/usr/include \
> --with-scalapack-lib=/usr/lib/libscalapack-lam.so \
> --with-mumps=1 --with-mumps-include=/usr/include \
> --with-mumps-lib=[/usr/lib/libdmumps.so,/usr/lib/libzmumps.so,/usr/lib/libsmumps.so,/usr/lib/libcmumps.so,/usr/lib/libmumps_common.so,/usr/lib/libpord.so]
> \
> --with-umfpack=1 --with-umfpack-include=/usr/include/suitesparse \
> --with-umfpack-lib=[/usr/lib/libumfpack.so,/usr/lib/libamd.so] \
> --with-spooles=1 --with-spooles-include=/usr/include/spooles \
> --with-spooles-lib=/usr/lib/libspooles.so \
> --with-hypre=1 --with-hypre-dir=/usr \
> --with-scotch=1 --with-scotch-include=/usr/include/scotch \
> --with-scotch-lib=/usr/lib/libscotch.so \
> --with-hdf5=1 --with-hdf5-dir=/usr
> ===============================================================================
> Configuring PETSc to compile on your system
> ===============================================================================
> TESTING: configureMkdir from
> config.programs(config/BuildSystem/config/programs.py:21)
> Illegal instruction
> make: *** [build-arch] Error 132
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
How annoying... I'll see what I can do.
Thanks again,
Adam
--
GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6
Engineering consulting with open source tools
http://www.opennovation.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20101108/d94a153d/attachment.pgp>
More information about the debian-science-maintainers
mailing list