I build all packages some time ago with binutils-gold and your package build without an hard failure, but I noticed that you seems to provide a library in a specific library package so other packages can link against it without problems.... but your shared object has still some unresolved symbols which the program which links agaomst it must resolve. This isnt a good idea because when you introduce new dependencies the package previously linked against the old version will break because it doesnt know about the new dependency. Maybe you could link against all needed libraries so programs must not link against libraries which it doesnt need to use. Maybe it is related to following bugs which hard failed due to unresolved symbols in programs http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=peter.fritzsche@gmx.de;tag=no-add-needed More informations can be found at http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking dpkg-shlibdeps already showed you the related warnings: dpkg-shlibdeps: warning: symbol lam_coll2pt used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol MPI_Iprobe used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol MPI_Get_count used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol ao_parse used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol MPI_Probe used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol MPI_Ssend_init used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol MPI_Type_create_hindexed used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol MPI_Allgather used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol MPI_Comm_spawn used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol MPI_Gather used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries. dpkg-shlibdeps: warning: 153 other similar warnings have been skipped (use -v to see them all).
This was mostly fixed in 2.2.3b8-12. The remaining six unresolved symbols below, used by /usr/lib/libxmpi.so.4.0, are actually found in /usr/bin/xmpi. dpkg-shlibdeps: warning: symbol _Z9xmpi_failPc used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries dpkg-shlibdeps: warning: symbol _Z18xmpi_ctl_resetinfov used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries dpkg-shlibdeps: warning: symbol _Z16xmpi_ctl_setinfoPc used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries dpkg-shlibdeps: warning: symbol _Z10xmpi_errorP10_WidgetRecPKcb used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries dpkg-shlibdeps: warning: symbol _Z9xmpi_busyv used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries dpkg-shlibdeps: warning: symbol _Z11xmpi_unbusyv used by debian/libxmpi4/usr/lib/libxmpi.so.4.0 found in none of the libraries