On Sun, 5 Feb 2017 15:49:32 +0500 Andrey Rahmatullin <w...@debian.org> wrote:
> On Sun, Feb 05, 2017 at 02:09:40PM +0500, Andrey Rahmatullin wrote:
> > undefined symbol: Cblacs_pinfo (/usr/lib/libblacs-openmpi.so.1.1)
> This one is defined in other two libs in the package.
>
> > undefined symbol: BI_Iam (/usr/lib/libblacsCinit-openmpi.so.1.1)
> > undefined symbol: BI_F77_MPI_COMM_WORLD
> > (/usr/lib/libblacsCinit-openmpi.so.1.1)
> > undefined symbol: BI_Np (/usr/lib/libblacsCinit-openmpi.so.1.1)
> > undefined symbol: bi_f77_get_constants_
> > (/usr/lib/libblacsCinit-openmpi.so.1.1)
> > undefined symbol: BI_BlacsErr (/usr/lib/libblacsCinit-openmpi.so.1.1)
> >
> > undefined symbol: BI_Iam (/usr/lib/libblacsF77init-openmpi.so.1.1)
> > undefined symbol: BI_F77_MPI_COMM_WORLD (/usr/lib/libblacsF77init-
> > openmpi.so.1.1)
> > undefined symbol: BI_Np (/usr/lib/libblacsF77init-openmpi.so.1.1)
> > undefined symbol: bi_f77_get_constants_ (/usr/lib/libblacsF77init-
> > openmpi.so.1.1)
> > undefined symbol: bi_f77_init_ (/usr/lib/libblacsF77init-openmpi.so.1.1)
> These ones are defined in the other library in the package.
>
> So this is is a circular dependency, unfortunately.
The fact that Cblacs_pinfo is provided by both
libblac{C,F77}init-openmpi looks intentional: one or the other should be
chosen at link time, depending on your preferred interface (C or F77).
Hence, it is not possible to enforce the dependency of libblacs-openmpi
on one or the other without breaking this flexibility.
By the way, does this bug really warrant a serious severity? I could not
find anything in the Policy mandating proper linking of shared libraries
within the same package.
--
.''`. Sébastien Villemot
: :' : Debian Developer
`. `' http://sebastien.villemot.name
`- GPG Key: 4096R/381A7594
