On 19 December 2007 at 20:38, [EMAIL PROTECTED] wrote: | > As you may know, we are trying to let Open MPI coexist with MPICH and | > LAM. | > | > /usr/include is fine for _non-conflicting_ files as good as a general | > rule, but not so clear if several packages provide it. By 'staying | > out of each others way' it is easier to build against several MPI | > implementations. | | I meant something like /usr/include/openmpi/
You lost me. Please make up your mind as to whether you think it is a problem because we do or do not use /usr/include, or /usr/include/openmpi ? We use /usr/include/openmpi now, and we think that's the right way: [EMAIL PROTECTED]:~$ dpkg -L libopenmpi-dev | grep mpi.h /usr/lib/openmpi/include/mpi.h /usr/lib/openmpi/include/openmpi/ompi/mpi/f77/prototypes_mpi.h [EMAIL PROTECTED]:~$ dpkg -l libopenmpi-dev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-======================================-======================================-============================================================================================ ii libopenmpi-dev 1.2.4-5 high performance message passing library -- header files [EMAIL PROTECTED]:~$ No bug here, and if you could excuse me now, I got real work to do. Dirk -- Three out of two people have difficulties with fractions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
