On Tue, Apr 01, 2008 at 11:13:16PM -0400, Adam C Powell IV wrote:
> Package: hdf5
> Version: 1.6.6-3
> Greetings,
> I'm afraid your rules file doesn't build openmpi libraries on the
> architectures where it's supposed to, so the openmpi packages are empty.
> Looking through the build logs on every architecture where it's supposed
> to work (amd64, ia64, sparc, powerpc), if I search the log for
> "openmpi", I get the package installation, a couple of symlinks at the
> top, then dh_makeshlibs at the very end, with no references to openmpi
> in between.  I don't understand why this is; your system seems sound and
> logical.
> I realize that I'm the cause of a lot of your openmpi troubles, having
> suggested this in the first place.  So I think I've come up with an
> elegant solution to this problem, found in the patch.  Instead of
> testing for the architecture in rules, each openmpi target just tests
> for the file /usr/lib/openmpi/include/mpi.h, and if it finds it,
> configures/builds/installs.  This patch works on amd64, haven't tested
> it elsewhere.
> The advantage of this approach is that when more arches support openmpi,
> you can just adjust the arch lists in control, and rules will
> automatically build the new openmpi packages.
> I hope this patch meets with your approval, and solves this problem of
> openmpi support once and for all.

I don't like that so much because OpenMPI detection should be done
without using paths which could be subject to changes due to
other maintainers' choices :-/ 
I'll try to find out why it does not work properly and how manage
better the issue.

Francesco P. Lovergine

Pkg-grass-devel mailing list

Reply via email to