[Pkg-openmpi-maintainers] Bug#848574: Fwd: Re: [open-mpi/ompi] Failure on mips64el (#2922)

[YunQiang Su]

The package in experimental (2.0.2-1) seems having no this problem.

On Sun, 5 Feb 2017 19:11:04 +0000 Alastair McKinstry
<alastair.mckinstry at sceal.ie> wrote:
> This hints at a linker issue on stretch
>
> -------- Forwarded Message --------
> Subject: Re: [open-mpi/ompi] Failure on mips64el (#2922)
> Date: Sun, 05 Feb 2017 09:18:36 -0800
> From: Paul H. Hargrove <notifications at github.com>
> Reply-To: open-mpi/ompi
> <reply+000df6ae2813a40fb4299d91cfa44a62cfe446305bee9acb92cf0000000114af206c92a169ce0c3b0d97 at reply.github.com>
>
> To: open-mpi/ompi <ompi at noreply.github.com>
> CC: Alastair McKinstry <alastair.mckinstry at sceal.ie>, Author
> <author at noreply.github.com>
>
>
>
> @ggouaillardet <https://github.com/ggouaillardet>
> Yes, I have both mips64 and mips64el and test thee ABIs
> (|-mabi={32,n32,64}|) on each.
> All 6 passed my testing of 2.0.2rc4, which included running the ring
> examples (|ring_{c,mpih,usempi,usempif08}|) with two ranks on 1 node.
> My tests are on Octeon II systems running Debian Wheezy, and are not
> mine to upgrade.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/open-mpi/ompi/issues/2922#issuecomment-277533817>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AA32rhNdErcRgpC2EaiaqjamKYwiI-_Xks5rZgRsgaJpZM4L2fjI>.
>