Hi all! Am Freitag, den 04.01.2008, 13:52 +0100 schrieb Ondrej Certik: > On Jan 4, 2008 1:40 PM, Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote: > > Ondrej Certik wrote: > > | In the last bug I reported: > > | > > | http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457088 > > | > > | I was told, that the mpi.h is in /usr/include/openmpi
No, you were told that it is in /usr/include/mpi. That's where mpi.h lives, in all Debian MPI packages out there. (Except MPICH, but that's a different story.) > > | However, in the clean environment, the libopenmpi-dev package fails to > > put mpi.h into > > | /usr/include/openmpi. It does so because that's not the place where mpi.h can be found, see above. > > | How about just using plain "ln -s"? Like this: > > | ln -s /usr/lib/openmpi/include/ /usr/include/openmpi This would break every other MPI implementation in Debian and therefore is not an option at all. That's what update-alternatives is for. > > Someone really needs to fix update-alternatives. > > Right. We should try to fix the real bug (update-alternatives). The bug has a patch and is pending. It should be fixed within the next dpkg uploads. I experienced very harsh words while working on this issue. It wasn't fun but it's resolved. However, in this case, update-alternatives is not to blame. You're looking for mpi.h at the wrong place. > Do you have some idea, where the problem is? See above. Using /usr/include/mpi should be totally fine. It also allows LAM users (or others) to port your package in case they need it. In other words: Don't make OpenMPI a requirement if you don't have to. If this does not solve your problem, I'll be glad to help you with your package. Best regards Manuel
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
