Bug#656189: petsc: Please disable hcp of the mpicc implementation

[Adam C Powell IV]

On Wed, 2012-01-18 at 10:36 -0500, Adam C Powell IV wrote:
> On Tue, 2012-01-17 at 12:03 +0100, Sylvestre Ledru wrote:
> > Source: petsc
> > Severity: important
> > Tags: patch
> > 
> > Hello,
> > 
> > It would be nice if you could apply the attached patch.
> > It disables the search of mpicc as hcp.
> > For an unclear reason, it fixes the bug #624671.
> > slepc fails to build under sparc if hcp is used (while mpiCC will work).
> 
> I don't understand, slepc 3.2 built just fine on sparc (so I closed
> 624671).  Is there a spurious package which provides a binary 'hcp'
> which perhaps PETSc should Build-Conflict with?

Okay, just checked and found hcp in lam4-dev, should have expected it
there.  This is now an obsolete problem because mpi-default-dev uses
mpich2 on non-openmpi architectures.

Since LAM is deprecated and end-of-life in Debian, can I close this bug
by adding lam4-dev to PETSc's Build-Conflicts?  People will still be
able to build using LAM by doing "debian/rules binary", as described in
README.Debian .

-Adam
-- 
GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Engineering consulting with open source tools
http://www.opennovation.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20120119/bdd91e77/attachment.pgp>