Orion Poplawski <orion-CVdf0l11yl+B+jHODAdFcQ@xxxxxxxxxxxxxxxx> writes: > On 11/21/2016 06:08 AM, Tuomo Soini wrote: >> On Mon, 21 Nov 2016 12:52:12 +0100 >> Antonio Trande <anto.trande@xxxxxxxxx> wrote: >> >>> Hi all. >>> >>> 'petsc' build is failing on epel7 because missing 'mpich-devel'; >>> however, devel package looks provides as >>> 'mpich-3.0-devel-3.0.4-10.el7.x86_64'. >>> >>> https://kojipkgs.fedoraproject.org//work/tasks/2209/16552209/root.log >>> >> >> Yes. 'hypre' needs fixing. petsc and hypre build for me in mock -- petsc also requires mpich-devel%{?_isa}, per guidelines. It looks as if you build them in koji currently, they won't install on CentOS/Scientific Linux. The problem is that Red Hat keep doing this sort of thing with MPI -- openmpi previously, without even working compatibility packages. It's not feasible to use their packages on a typical production HPC system (IMNSHO as someone who made the mistake of trying to). That's compounded by things in EPEL like Scalapack needlessly changing ABI. Rpm packaging keeps looking less attractive, unfortunately. > FWIW, I've filed https://bugzilla.redhat.com/show_bug.cgi?id=1397192 for the > missing provides. [Contrary to what it says there, the mpich-3.0 packaging has the provide, but it's obsoleted by 3.2.] _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
