Source: pgapack
Version: 1.1.1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161219 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh_testdir
> test -d /usr/lib/openmpi && \
>               ./configure -arch linux -cc gcc -cflags "-O3 -fPIC -D_REENTRANT 
> -Wall" \
>                       -mpiinc /usr/lib/openmpi/include -mpilib 
> /usr/lib/libmpi.so && \
>               cd source && /usr/bin/make && cd -
> debian/rules:37: recipe for target 'build-stamp' failed
> make: [build-stamp] Error 1 (ignored)
> test -d /usr/include/mpich2 && \
>               ./configure -arch linux -cc mpicc.mpich2 -cflags "-O3 -fPIC 
> -D_REENTRANT -Wall" \
>                       -mpiinc /usr/include/mpich2 -mpilib 
> /usr/lib/libmpich.so && \
>               cd source && /usr/bin/make && cd -
> debian/rules:37: recipe for target 'build-stamp' failed
> make: [build-stamp] Error 1 (ignored)
> test -d /usr/include/lam && \
>               ./configure -arch linux -cc gcc -cflags "-O3 -fPIC -D_REENTRANT 
> -Wall" \
>                       -mpiinc /usr/include/lam -mpilib /usr/lib/liblam.so && \
>               cd source && /usr/bin/make && cd -
> debian/rules:37: recipe for target 'build-stamp' failed
> make: [build-stamp] Error 1 (ignored)
> (cd lib/linux/                && \
>               mv -v libpgaO.a libpgapack-mpi1.a && \
>               gcc -shared -Wl,-soname,libpgapack-mpi1.so.1 -o 
> libpgapack-mpi1.so.1.0 *.o && \
>               rm *.o)
> /bin/sh: 1: cd: can't cd to lib/linux/
> debian/rules:37: recipe for target 'build-stamp' failed
> make: *** [build-stamp] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2016/12/19/pgapack_1.1.1-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Reply via email to