Re: [OMPI users] Debian MPI -- mpirun missing
Hi all, Dirk Eddelbuettel wrote: On 18 October 2008 at 03:30, Terry Frankcombe wrote: | | But again, this is a discussion for the Debian list. In particularly for the 'package Open MPI maintainers' list at http://lists.alioth.debian.org/mailman/listinfo/pkg-openmpi-maintainers so if you want to continue this discussion, please take there. Thanks a lot, Dirk; I'll take my Debian problems over to that list then! I didn't realize that this had to be a Debian-specific problem; I know so little, I was even open to a response like, "No, there is no mpirun anymore". Of course, if mpirun is just an alias to orterun, then I will just do that (use orterun instead). The system administrator of one of the machines I'll use prefers to stick to Debian packages, despite their age, so unless I can find a good reason (serious security flaw), I guess doing this is far easier (politically) than installing from source. Thank you all for your help! Ray
Re: [OMPI users] Debian MPI -- mpirun missing
On 18 October 2008 at 03:30, Terry Frankcombe wrote: | | > Well when I use Open MPI I go with the new convention and call orterun | > instead of mpirun. I think you should have. Maybe a local alias in your | > ~/.bashrc can do the trick. | > | > Current packages do have mpirun.openmpi but we were unable to devise a | > bullet-proof scheme between lam, mpich and Open MPI for sharing / updating / | > ... the alternatives links as there are sublte differences that prevent us | > from switching all these aliases consistently. | | Eh? Surely it's a simple case of conflict? If you want multiple It is not simple or else we'd do it. Trust us, several folks tried. IIRC one of the issues was that among mpich, lam and Open MPI, the set of supplied and potential conflicting apps (and their manual pages etc) is not perfectly overlapping. | packages providing similar functionality, it's up to you to specify how | the user should chose which one they want to run. Breaking any | particular package (or all packages) seems like a particularly poor | choice, but that's only my opinion. | | I would argue that orterun is a very long way from a "new convention". | I'd draw attention to section 8.8 of the MPI 2.1 standard. | | But again, this is a discussion for the Debian list. In particularly for the 'package Open MPI maintainers' list at http://lists.alioth.debian.org/mailman/listinfo/pkg-openmpi-maintainers so if you want to continue this discussion, please take there. We can also point you to a couple of discussion in the Debian bug tracking system, for example http://bugs.debian.org/452047 where Manuel actually goes through the motions. If you think you have fixes for this 'simple case of conflict', as you call, do not hold back and tell us, but please over on that list. Thank you, Dirk -- Three out of two people have difficulties with fractions.
Re: [OMPI users] Debian MPI -- mpirun missing
> Well when I use Open MPI I go with the new convention and call orterun > instead of mpirun. I think you should have. Maybe a local alias in your > ~/.bashrc can do the trick. > > Current packages do have mpirun.openmpi but we were unable to devise a > bullet-proof scheme between lam, mpich and Open MPI for sharing / updating / > ... the alternatives links as there are sublte differences that prevent us > from switching all these aliases consistently. Eh? Surely it's a simple case of conflict? If you want multiple packages providing similar functionality, it's up to you to specify how the user should chose which one they want to run. Breaking any particular package (or all packages) seems like a particularly poor choice, but that's only my opinion. I would argue that orterun is a very long way from a "new convention". I'd draw attention to section 8.8 of the MPI 2.1 standard. But again, this is a discussion for the Debian list.
Re: [OMPI users] Debian MPI -- mpirun missing
On 18 October 2008 at 00:16, Raymond Wan wrote: | | Hi all, | | I'm very new to MPI and am trying to install it on to a Debian Etch | system. I did have mpich installed and I believe that is causing me Etch is getting old, and its Open MPI 1.1 package were in suboptimal shape. A few of us get together as a new Open MPI team within Debian, and 1.2.* packages are in much better shape. So please try to get 1.2 packages. | problems. I completely uninstalled it and then ran: | | update-alternatives --remove-all mpicc | | Then, I installed the following packages: | | libibverbs1 openmpi-bin openmpi-common openmpi-libs0 openmpi-dbg openmpi-dev | | And it now says: | | >> update-alternatives --display mpicc | mpicc - status is auto. | link currently points to /usr/bin/mpicc.openmpi | /usr/bin/mpicc.openmpi - priority 40 | slave mpif90: /usr/bin/mpif90.openmpi | slave mpiCC: /usr/bin/mpic++.openmpi | slave mpic++: /usr/bin/mpic++.openmpi | slave mpif77: /usr/bin/mpif77.openmpi | slave mpicxx: /usr/bin/mpic++.openmpi | Current `best' version is /usr/bin/mpicc.openmpi. | | which seems ok to me... So, I tried to compile something (I had sample | code from a book I purchased a while back, but for mpich), however, I | can run the program as-is, but I think I should be running it with | mpirun -- the FAQ suggests there is one? But, there is no mpirun | anywhere. It's not in /usr/bin. I updated the filename database | (updatedb) and tried a "locate mpirun", and I get only one hit: Well when I use Open MPI I go with the new convention and call orterun instead of mpirun. I think you should have. Maybe a local alias in your ~/.bashrc can do the trick. Current packages do have mpirun.openmpi but we were unable to devise a bullet-proof scheme between lam, mpich and Open MPI for sharing / updating / ... the alternatives links as there are sublte differences that prevent us from switching all these aliases consistently. Hope this helps, Dirk | | /usr/include/openmpi/ompi/runtime/mpiruntime.h | | Is there a package that I neglected to install? I did an "aptitude | search openmpi" and installed everything listed... :-) Or perhaps I | haven't removed all trace of mpich? | | Thank you in advance! | | Ray | | | ___ | users mailing list | us...@open-mpi.org | http://www.open-mpi.org/mailman/listinfo.cgi/users -- Three out of two people have difficulties with fractions.
Re: [OMPI users] Debian MPI -- mpirun missing
On Sat, 2008-10-18 at 00:16 +0900, Raymond Wan wrote: > > Is there a package that I neglected to install? I did an "aptitude > search openmpi" and installed everything listed... :-) Or perhaps I > haven't removed all trace of mpich? According to packages.debian.org there isn't a openmpi pacakge which contains mpirun which as you note isn't expected. There is a orterun however which you could use instead. The Etch version of openmpi is very old, openmpi has made a lot of progress since 1.1-2.3, I'd recommend building from source if you are able to. Ashley.
Re: [OMPI users] Debian MPI -- mpirun missing
Er, shouldn't this be in the Debian support list? A correctly installed OpenMPI will give you mpirun. If their openmpi-bin package doesn't, then surely it's broken? (Or is there a straight openmpi package?) On Sat, 2008-10-18 at 00:16 +0900, Raymond Wan wrote: > Hi all, > > I'm very new to MPI and am trying to install it on to a Debian Etch > system. I did have mpich installed and I believe that is causing me > problems. I completely uninstalled it and then ran: > > update-alternatives --remove-all mpicc > > Then, I installed the following packages: > > libibverbs1 openmpi-bin openmpi-common openmpi-libs0 openmpi-dbg openmpi-dev > > And it now says: > > >> update-alternatives --display mpicc > mpicc - status is auto. > link currently points to /usr/bin/mpicc.openmpi > /usr/bin/mpicc.openmpi - priority 40 > slave mpif90: /usr/bin/mpif90.openmpi > slave mpiCC: /usr/bin/mpic++.openmpi > slave mpic++: /usr/bin/mpic++.openmpi > slave mpif77: /usr/bin/mpif77.openmpi > slave mpicxx: /usr/bin/mpic++.openmpi > Current `best' version is /usr/bin/mpicc.openmpi. > > which seems ok to me... So, I tried to compile something (I had sample > code from a book I purchased a while back, but for mpich), however, I > can run the program as-is, but I think I should be running it with > mpirun -- the FAQ suggests there is one? But, there is no mpirun > anywhere. It's not in /usr/bin. I updated the filename database > (updatedb) and tried a "locate mpirun", and I get only one hit: > > /usr/include/openmpi/ompi/runtime/mpiruntime.h > > Is there a package that I neglected to install? I did an "aptitude > search openmpi" and installed everything listed... :-) Or perhaps I > haven't removed all trace of mpich? > > Thank you in advance! > > Ray > > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users
[OMPI users] Debian MPI -- mpirun missing
Hi all, I'm very new to MPI and am trying to install it on to a Debian Etch system. I did have mpich installed and I believe that is causing me problems. I completely uninstalled it and then ran: update-alternatives --remove-all mpicc Then, I installed the following packages: libibverbs1 openmpi-bin openmpi-common openmpi-libs0 openmpi-dbg openmpi-dev And it now says: >> update-alternatives --display mpicc mpicc - status is auto. link currently points to /usr/bin/mpicc.openmpi /usr/bin/mpicc.openmpi - priority 40 slave mpif90: /usr/bin/mpif90.openmpi slave mpiCC: /usr/bin/mpic++.openmpi slave mpic++: /usr/bin/mpic++.openmpi slave mpif77: /usr/bin/mpif77.openmpi slave mpicxx: /usr/bin/mpic++.openmpi Current `best' version is /usr/bin/mpicc.openmpi. which seems ok to me... So, I tried to compile something (I had sample code from a book I purchased a while back, but for mpich), however, I can run the program as-is, but I think I should be running it with mpirun -- the FAQ suggests there is one? But, there is no mpirun anywhere. It's not in /usr/bin. I updated the filename database (updatedb) and tried a "locate mpirun", and I get only one hit: /usr/include/openmpi/ompi/runtime/mpiruntime.h Is there a package that I neglected to install? I did an "aptitude search openmpi" and installed everything listed... :-) Or perhaps I haven't removed all trace of mpich? Thank you in advance! Ray