Your message dated Fri, 4 Jan 2008 16:46:46 +0100
with message-id <[EMAIL PROTECTED]>
and subject line [Pkg-openmpi-maintainers] Bug#459070: Bug#459070: 
/usr/include/openmpi is missing (mpi.h isn't in /usr/include/**)
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: libopenmpi-dev
Severity: normal

--- Please enter the report below this line. ---

Hi, 

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

However, in the clean environment, the libopenmpi-dev package fails to put 
mpi.h into
/usr/include/openmpi.

How to reproduce the problem:

$ sudo cowbuilder --update     # or --c 500 unstable        debian.certik.cz 
reate if you never used cowbuilder before
$ sudo cowbuilder --login
# apt-get install libopenmpi-dev
# ls /usr/include/openmpi
ls: /usr/include/openmpi: No such file or directory

In the last bug, it was suggested, that this could be a problem in the broken
update-alternatives package. This could be the real problem, but unfortunately,
as a consequence, libopenmpi-dev isn't working. I am reporting this bug
as a normal bug, but I think the severity is serious, because it's a violation
of the FHS not to put the *.h files into /usr/include or any subdirectory.

How about just using plain "ln -s"? Like this:

ln -s /usr/lib/openmpi/include/ /usr/include/openmpi

This should fix the problem, if update-alternatives doesn't work.

Ondrej

--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.23-1-686

Debian Release: lenny/sid
  500 unstable        ftp.cz.debian.org 

--- Package information. ---
Depends              (Version) | Installed
==============================-+-============
libopenmpi1        (= 1.2.4-5) | 1.2.4-5
openmpi-common     (= 1.2.4-5) | 1.2.4-5





--- End Message ---
--- Begin Message ---
> | 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.
>
> In fact this is critically important because Open MPI exists only a handful
> architectures.  I maintain packages that have Build-Depends on Open MPI where
> available and on LAM where not.
>
> | If this does not solve your problem, I'll be glad to help you with your
> | package.
>
> Seconded. Ondrej, feel free to study other packages setup for builds under
> the MPI packages.


Yes, you are of course right. I don't know what I was thinking.
The mpi.h is of course in /usr/include/mpi.h and it works.
Sorry about that!

Ondrej


--- End Message ---

Reply via email to