[mpich-discuss] query ABI version

Jeff Hammond jeff.science at gmail.com
Mon Feb 23 13:05:17 CST 2015


Why not keep the ABI defined in the devel version?  Shouldn't you be
able to keep the ABI well-defined and change it when it needs
changing?

In any case, I do not really care.  This is about querying the ABI of
well-defined releases of MPICH and its derivatives.

For example, I want to be able to download a release of MPICH, build a
library against it and then be able to redistribute that library to
users that might build their application with Cray MPI or Intel MPI.
As a responsible library developer, I want to detect any ABI problems
as early as possible rather than have potentially silent errors.
Right now, it seems rather difficult for me to do this.

Jeff

On Sun, Feb 22, 2015 at 4:35 AM, Balaji, Pavan <balaji at anl.gov> wrote:
>
>> On Feb 20, 2015, at 1:32 PM, Wesley Bland <wbland at anl.gov> wrote:
>> Obviously, that’s pretty terrible to try to parse for a user. Also, in unreleased versions, those numbers will remain 0. It’s just in tarballs that the number will be updated.
>
> It's updated only in stable releases.  Alpha, beta, RC releases all keep it at 0:0:0.
>
>   -- Pavan
>
> --
> Pavan Balaji  ✉️
> http://www.mcs.anl.gov/~balaji
>
> _______________________________________________
> discuss mailing list     discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss



-- 
Jeff Hammond
jeff.science at gmail.com
http://jeffhammond.github.io/
_______________________________________________
discuss mailing list     discuss at mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss


More information about the discuss mailing list