Bug#653616: libmpich2-dev: Missing library linkage for libmpich.so on MIPS(el) and S390

[Pavan Balaji]

Hi Adam,

On 01/11/2012 04:10 PM, Adam C Powell IV wrote:
>> In what way are they breaking?  We'd like to hear about such issues and
>> get them fixed.
>
> See the previous emails: when one links a library or executable with
> "-lmpi", and libmpi.so is linked to libmpich.so, then it breaks with
> undefined symbols which all start with MPL_ .

Ah, OK.  I thought you were referring to a different problem.

> I meant inter-library dependencies, for the shared library (not the
> static one).  I believe that libtool is intelligent enough so that if
> you give it the dependency libs it will decide based on the platform
> whether and how to do the linking.
>
> Then again, mpich2 seems to use its own createshlib script instead of
> libtool.  But it has the dependentLibs variable which includes all of
> the -L and -l on the command line, so "-Lmpl -lmpl" should work -- on
> platforms that support it.
>
> Perhaps the simplest way is to do this as a Debian-only patch to the
> top-level Makefile.in applied at build time from the debian/patches
> directory, like the destdir patch.  What do you think?

Up till mpich2 1.4.x, we were using a combination of 
createshlib+autotools+simplemake, which was a mess.  In 1.5.x we have 
moved to completely using autotools for all of mpich2.

For the inter-library dependencies, I'd not like to have a Debian-only 
patch.  But you are right, libtool should be able to disable 
dependencies on platforms it doesn't support.  Let me look into this 
some more.

Btw, the destdir patch should not be required in 1.5.x.

  -- Pavan

-- 
Pavan Balaji
http://www.mcs.anl.gov/~balaji