Am Mittwoch, den 07.04.2010, 13:12 -0500 schrieb Pavan Balaji:
> Ok, this is the part I didn't understand fully. Is MPICH2's build
> failing when includedir is specified as a different location? (I just
> tried that on my machine and it seems to work correctly for me.) Or did
> you mean some other package depending on MPICH2 is failing?
Packages depending on MPICH2 are failing to build. This is not an issue
with MPICH2, but thanks for taking the time to look into it!
The problem is that a lot of build systems of MPI-using software want
the headers in $prefix/include and the libs in $prefix/lib, and on can
often only use $prefix to point to the location of MPI-relevant files.
The Debian package of MPICH2 uses $prefix/lib and $prefix/include/mpich2
which a lot of build systems do not like or handle correctly. This is
why the openmpi package uses --prefix=/usr/lib/openmpi to build and
symlinks the libraries to /usr/lib. This way, everything works as
expected. Not pretty, but effective. The questions is whether we apply
that change to the mpich2 package, as it was for all MPI packages in
Debian so far, or fix every broken build system out there. [0]
Still waiting for the day when MPI standardizes on ABI, not API… But
that may be wishful thinking.
Best regards,
Manuel
[0] Preferably, we would fix the build system. As far as Open MPI is
concerned, the /usr/lib/openmpi/{lib,include} hierarchy was requested by
a user since he had the very same problem.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
