Bug#822971: dolfin: FTBFS on kfreebsd

2017-04-03 Thread Drew Parsons
tags 822971 + fixed pending thanks A fix to build dolfin on kfreebsd is in git 2016.2.0-3, pending upload. Drew

Bug#822971: dolfin: FTBFS on kfreebsd

2016-10-06 Thread Mattia Rizzolo
On Thu, Oct 06, 2016 at 04:52:04PM +0800, Drew Parsons wrote: > On Sat, 17 Sep 2016 11:29:54 +0800 Drew Parsons > wrote: > > ... It's not yet built at the moment due to > > other build-dependencies higher up the chain. > > Specifically, mpi4py (python-mpi4py) is not

Bug#822971: dolfin: FTBFS on kfreebsd

2016-10-06 Thread Drew Parsons
On Sat, 17 Sep 2016 11:29:54 +0800 Drew Parsons wrote: > ... It's not yet built at the moment due to > other build-dependencies higher up the chain. Specifically, mpi4py (python-mpi4py) is not currently building on kfreebsd.

Bug#822971: dolfin: FTBFS on kfreebsd

2016-09-16 Thread Drew Parsons
On Fri, 29 Apr 2016 13:46:07 + Mattia Rizzolo wrote: >  > Since this version, with the switch to vtk6 and whatnot, dolfin FTBFS on > kfreebsd. Looks like this was a transient failure.  dolfin later built successfully in kfreebsd.  It's not yet built at the moment due to

Bug#822971: dolfin: FTBFS on kfreebsd

2016-04-29 Thread Mattia Rizzolo
Source: dolfin Version: 1.6.0-4 Control: block 822321 by -1 Since this version, with the switch to vtk6 and whatnot, dolfin FTBFS on kfreebsd. This unfortunately jeopardize our quest to remove vtk5 from the archive, as the old binaries there still depends on it. Please try to see what causes