[mpich-discuss] Wrong symlinks when using MPILIBNAME

[Balaji, Pavan]

Umm.  Sorry, that's my bad.  Some overaggressive backward compatibility additions I did a few months ago.  I'll work on a fix.

  -- Pavan





On 10/21/15, 9:30 AM, "Torquil Macdonald Sørensen" <torquil at gmail.com> wrote:

>If I set MPILIBNAME=mpich when running the configure script, I end up
>with some wrong symlinks among the libraries.
>
>Inside /usr/lib, I get two links that point to themselves:
>
>libmpich.so -> libmpich.so
>libmpichcxx.so -> libmpichcxx.so
>
>They should be:
>
>libmpich.so -> libmpich.so.0.0.0
>libmpichcxx.so -> libmpichcxx.so.0.0.0
>
>On the other hand, the corresponding symlink for the fortran library is
>correct:
>
>libmpichfort.so -> libmpichfort.so.0.0.0
>
>I'm using 3.2rc1 and building with
>
>$ gcc --version
>gcc (GCC) 5.2.1 20151020
>
>If I don't set MPILIBNAME, the resulting libmpi* library files have
>correct symlinks.
>
>Best regards
>Torquil Macdonald Sørensen
>
>_______________________________________________
>discuss mailing list     discuss at mpich.org
>To manage subscription options or unsubscribe:
>https://lists.mpich.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list     discuss at mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss