On Jan 4, 2008 1:40 PM, Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
>
> On 4 January 2008 at 12:24, Ondrej Certik wrote:
> | 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.
>
> Are you sure? We then stop to cooperate nicely with LAM and MPICH2, and that
> is NOT the Debian way.
>
> Someone really needs to fix update-alternatives.

Right. We should try to fix the real bug (update-alternatives).

Do you have some idea, where the problem is?

Ondrej



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to