Glenn, If you're careful with $PATH and $LD_LIBRARY_PATH you can certainly do this. One thing that makes this a little easier is the 'modules' package (http://modules.sourceforge.net/). We use this to maintain 9 versions of OpenMPI for various reasons, along with 5 versions of LAM and a version of MPICH. It does a nice job of keeping everything separate and our uses have grasped it pretty quickly.
Good luck. --andy > -----Original Message----- > From: users-boun...@open-mpi.org > [mailto:users-boun...@open-mpi.org] On Behalf Of Glenn Johnson > Sent: Thursday, September 28, 2006 3:04 PM > To: us...@open-mpi.org > Subject: [OMPI users] using both 64 and 32 bit mpi > > I have an 8-way AMD64 system. I built a 64 bit open-mpi-1.1 > implementation and then compiled software to use it. That all > works fine. > > In addition, I have a 32 bit binary program (Schrodinger > Jaguar) that I would like to run on this machine with mpi. > Schrodinger provides source code to build an mpi > compatibility layer. This compatibility layer allows jaguar > to use a different mpi implementation than that which the > software was compiled with. I do not want to give up the 64 > bit open-mpi that I already have and am using. > > So my questions are: > 1. Can I build/install a 32 bit version of open-mpi even though I > already have a 64 bit version installed? > 2. What "tricks" might I need to do to make sure a program calls > the correct version of mpi (32 or 64 bit)? > 3. Would I do better considering running jaguar in a 32 > bit chroot > environment? > > Thanks. > > -- > Glenn Johnson <gjohn...@srrc.ars.usda.gov> USDA, ARS, SRRC > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users >
