On Sun, 06 Oct 2013, David Suárez wrote: > Source: mpi4py > Version: 1.3+hg20130509-1 > Severity: serious > Tags: jessie sid > User: [email protected] > Usertags: qa-ftbfs-20131006 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): > > MPI configuration: [mpi] from 'mpi.cfg' > > MPI C compiler: /usr/bin/mpicc > > MPI C++ compiler: /usr/bin/mpicxx > > checking for library 'pthread' ... > > /usr/bin/mpicc -fPIC -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall > > -Wstrict-prototypes -c _configtest.c -o _configtest.o > > /usr/bin/mpicc _configtest.o -lpthread -o _configtest > > success! > > removing: _configtest.c _configtest.o _configtest > > checking for library 'mpe' ... > > /usr/bin/mpicc -fPIC -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall > > -Wstrict-prototypes -c _configtest.c -o _configtest.o > > /usr/bin/mpicc _configtest.o -lmpe -lpthread -o _configtest > > /usr/bin/ld: cannot find -lmpe > > collect2: error: ld returned 1 exit status > The full build log is available from: > > http://aws-logs.debian.net/ftbfs-logs/2013/10/06/mpi4py_1.3+hg20130509-1_unstable.log Thanks for the full log -- this issue had nothing to do with -lmpe message which was benign course of discovery present libraries. Actual failure, as logical to expect, was at the end: make[1]: Leaving directory `/«BUILDDIR»/mpi4py-1.3+hg20130509' dh_installdocs -O--buildsystem=python_distutils cp: not writing through dangling symlink '/«BUILDDIR»/mpi4py-1.3+hg20130509/debian/python-mpi4py-doc/usr/share/doc/python-mpi4py-doc/html/_static/jquery.js' dh_installdocs: cd 'docs/source/usrman/_build/html/..' && find 'html' \( -type f -or -type l \) -and ! -empty -print0 | xargs -0 -I {} cp --parents -dp {} /«BUILDDIR»/mpi4py-1.3+hg20130509/debian/python-mpi4py-doc/usr/share/doc/python-mpi4py-doc returned exit code 123 make: *** [binary] Error 123 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 which could have been due to internal issue in python-sphinx. I will close this issue if build succeeds in a clean up-to-date sid chroot . Cheers, -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
