Bug#854228: Libraries not linked with their deps

2017-07-25 Thread Drew Parsons
On Tue, 21 Mar 2017 11:03:07 +0800 Drew Parsons wrote: > On Tue, 21 Mar 2017 10:50:29 +0800 Drew Parsons > wrote: > >  > > That document is from 1997 though.  The MPI standard has moved > through > > 2 major versions since then. But blacs remains unchanged. >  > Further, BLACS is now part of (pac

Bug#854228: Libraries not linked with their deps

2017-03-25 Thread Muammar El Khatib
Dear all, On Mon, Mar 20, 2017 at 11:03 PM, Drew Parsons wrote: > Probably the solution we want is to update our scalapack to 2.0.2, and > remove this blacs package, at least as a separate source package. That > won't happen for stretch, obviously. I am sorry for the delay in replying to this re

Bug#854228: Libraries not linked with their deps

2017-03-20 Thread Drew Parsons
On Tue, 21 Mar 2017 10:50:29 +0800 Drew Parsons wrote: >  > That document is from 1997 though.  The MPI standard has moved through > 2 major versions since then. But blacs remains unchanged. Further, BLACS is now part of (packaged with) scalapack, see http://netlib.org/scalapack/scalapack-2.0.0.h

Bug#854228: Libraries not linked with their deps

2017-03-20 Thread Drew Parsons
On Wed, 08 Feb 2017 14:25:12 +0100 =?ISO-8859-1?Q?S=E9bastien?= Villemot wrote: >  > I don't know what's the proper solution to this issue. The circularity > can easily be dealt with (using patchelf for closing the loop in > DT_NEEDED entries). >  > The problem is rather that the Cblacs_pinfo symb

Bug#854228: Libraries not linked with their deps

2017-02-08 Thread Sébastien Villemot
Le mercredi 08 février 2017 à 17:48 +0500, Andrey Rahmatullin a écrit : > On Wed, Feb 08, 2017 at 01:21:13PM +0100, Sébastien Villemot wrote: > > 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 > >

Bug#854228: Libraries not linked with their deps

2017-02-08 Thread Andrey Rahmatullin
On Wed, Feb 08, 2017 at 01:21:13PM +0100, Sébastien Villemot wrote: > 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. You are correct, "within the same package" is not a pa

Bug#854228: Libraries not linked with their deps

2017-02-08 Thread Sébastien Villemot
On Sun, 5 Feb 2017 15:49:32 +0500 Andrey Rahmatullin 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(/

Bug#854228: Libraries not linked with their deps

2017-02-05 Thread Andrey Rahmatullin
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_CO

Bug#854228: Libraries not linked with their deps

2017-02-05 Thread Andrey Rahmatullin
Package: libblacs-openmpi1 Version: 1.1-37+b1 Severity: serious All three shared libs in the package are linked only with libc, while using various MPI_*, BI_* etc symbols. Interesting that rebuilding a package (with the patch for #848813) links these libraries with various libmpi_* libs, partial