Hello Mattia,
On 04.08.2016 12:49, Mattia Rizzolo wrote:
> On Thu, Aug 04, 2016 at 12:02:51PM +0200, Helge Deller wrote:
>> Currently I've stopped all hppa buildds and plan to upgrade them to gcc6
>> before starting them again. And, I've started a test build of boost1.6.1
>> to check if the mpi-de
Hi all,
On 04/08/2016 11:02, Helge Deller wrote:
> Hi Mattia,
>
>> On Thu, Aug 04, 2016 at 09:34:35AM +0200, Helge Deller wrote:
>>> mpi-defaults depends on libmpich-dev for the hppa architecture (like m68k
>>> and sh4).
>>> All other architectures use libopenmpi-dev.
>>> Is there a reason for t
On Thu, Aug 04, 2016 at 12:02:51PM +0200, Helge Deller wrote:
> > > The openmpi packages builds successfully on hppa, so I'd suggest to switch
> > > to openmpi for hppa (and maybe m68k and sh4?) too.
> >
> > notice that switching default means rebuilding all the rdep in the
> > correct order (ben
Hi Mattia,
> On Thu, Aug 04, 2016 at 09:34:35AM +0200, Helge Deller wrote:
> > mpi-defaults depends on libmpich-dev for the hppa architecture (like m68k
> > and sh4).
> > All other architectures use libopenmpi-dev.
> > Is there a reason for that?
>
> reason is that at that time openmpi was not a
On Thu, Aug 04, 2016 at 09:34:35AM +0200, Helge Deller wrote:
> mpi-defaults depends on libmpich-dev for the hppa architecture (like m68k and
> sh4).
> All other architectures use libopenmpi-dev.
> Is there a reason for that?
reason is that at that time openmpi was not available on those
architec
Package: mpi-defaults
Version: 1.6
mpi-defaults depends on libmpich-dev for the hppa architecture (like m68k and
sh4).
All other architectures use libopenmpi-dev.
Is there a reason for that?
The openmpi packages builds successfully on hppa, so I'd suggest to switch
to openmpi for hppa (and maybe
