Re: [OMPI users] Compiling HPCC with OpenMPI
Hi Jeff, I had noticed the the library name switched but thanks for pointing it out still ;) As for the compilation route, I chose to use mpicc as the preferred approach and indeed let the wrapper do the work. FWIW, I got HPCC running, now to find a nice way to sort through all the data ;) Eric Le lundi 26 février 2007 06:53, Jeff Squyres a écrit : > Note that George listed the v1.2 OMPI libraries (-lopen-rte and - > lopenpal) -- the v.1.1.x names are slightly different (-lorte and - > lopal). We had to change the back-end library names between v1.1 and > v1.2 because someone else out in the Linux community uses "libopal". > > I typically prefer using "mpicc" as CC and LINKER and therefore > letting the OMPI wrapper handle everything for exactly this reason. > > > On Feb 21, 2007, at 12:39 PM, Eric Thibodeau wrote: > > > Hi George, > > > > Would you say this is preferred to changing the default CC + LINKER? > > Eric > > Le mercredi 21 février 2007 12:04, George Bosilca a écrit : > >> You should use something like this > >> MPdir = /usr/local/mpi > >> MPinc = -I$(MPdir)/include > >> MPlib = -L$(MPdir)/lib -lmpi -lopen-rte -lopen-pal > >> > >>george. > > > > ___ > > users mailing list > > us...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/users > > -- Eric Thibodeau Neural Bucket Solutions Inc. T. (514) 736-1436 C. (514) 710-0517
Re: [OMPI users] Compiling HPCC with OpenMPI
Note that George listed the v1.2 OMPI libraries (-lopen-rte and - lopenpal) -- the v.1.1.x names are slightly different (-lorte and - lopal). We had to change the back-end library names between v1.1 and v1.2 because someone else out in the Linux community uses "libopal". I typically prefer using "mpicc" as CC and LINKER and therefore letting the OMPI wrapper handle everything for exactly this reason. On Feb 21, 2007, at 12:39 PM, Eric Thibodeau wrote: Hi George, Would you say this is preferred to changing the default CC + LINKER? Eric Le mercredi 21 février 2007 12:04, George Bosilca a écrit : You should use something like this MPdir = /usr/local/mpi MPinc = -I$(MPdir)/include MPlib = -L$(MPdir)/lib -lmpi -lopen-rte -lopen-pal george. ___ users mailing list us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users -- Jeff Squyres Server Virtualization Business Unit Cisco Systems
Re: [OMPI users] Compiling HPCC with OpenMPI
You should use something like this MPdir = /usr/local/mpi MPinc = -I$(MPdir)/include MPlib = -L$(MPdir)/lib -lmpi -lopen-rte -lopen-pal george. On Feb 21, 2007, at 11:35 AM, Eric Thibodeau wrote: Hello all, As we all know, compiling OpenMPI is not a matter of adding -lmpi (http://www.open-mpi.org/faq/?category=mpi-apps). I have tried many different approaches on configuring the 3 crucial MPI lines in the HPCC Makefiles with no success. There seems to be no correct way to get mpicc --shome:* to return the correct info and forcing the correct paths/info seems to be incorrect (ie, what OpenMPI lib do I point to here: MPlib = $(MPdir)/lib/libmpich.a) Any help would be greatly appreciated! Exerp from the Makefile: # -- # - Message Passing library (MPI) -- # -- # MPinc tells the C compiler where to find the Message Passing library # header files, MPlib is defined to be the name of the library to be # used. The variable MPdir is only used for defining MPinc and MPlib. # MPdir= /usr/local/mpi MPinc= -I$(MPdir)/include MPlib= $(MPdir)/lib/libmpich.a -- Eric Thibodeau ___ users mailing list us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users
Re: [OMPI users] Compiling HPCC with OpenMPI
Thanks Laurent, I will try your proposed settings. Note that I didn't want to use CC= and LINKER= since I dont know the probable impacts on the rest of the benchmarks...hmm...though this IS a clustering benchamrk. Also note that I wasn't trying to compile for MPICH, I merely copied the lines from a "clean" config as a reference ;) Eric Le mercredi 21 février 2007 11:48, Laurent Nguyen a écrit : > Hello, > > I believe that you are trying to use mpich, not openmpi (libmpich.a). > Personnally, I've compiling HPCC on AIX IBM with OpenMPI with theses lines: > > # -- > # - Message Passing library (MPI) -- > # -- > # MPinc tells the C compiler where to find the Message Passing library > # header files, MPlib is defined to be the name of the library to be > # used. The variable MPdir is only used for defining MPinc and MPlib. > # > MPdir= > MPinc= > MPlib= > ... > CC = mpicc > > LINKER = mpicc > > But, in my environnment variable $PATH, I've the directory where OpenMPI > executables are: //openmpi/bin > > I hope I could help you... > > Regards > > > ** > NGUYEN Anh-Khai Laurent - Ingénieur de Recherche > Equipe Support Utilisateur > > Email:laurent.ngu...@idris.fr > Tél :01.69.35.85.66 > Adresse :IDRIS - Institut du Développement et des Ressources en >Informatique Scientifique >CNRS >Batiment 506 >BP 167 >F - 91403 ORSAY Cedex > Site Web :http://www.idris.fr > ** > > Eric Thibodeau a écrit : > > Hello all, > > > > As we all know, compiling OpenMPI is not a matter of adding -lmpi > > (http://www.open-mpi.org/faq/?category=mpi-apps). I have tried many > > different approaches on configuring the 3 crucial MPI lines in the HPCC > > Makefiles with no success. There seems to be no correct way to get mpicc > > --shome:* to return the correct info and forcing the correct paths/info > > seems to be incorrect (ie, what OpenMPI lib do I point to here: MPlib = > > $(MPdir)/lib/libmpich.a) > > > > Any help would be greatly appreciated! > > > > Exerp from the Makefile: > > > > # -- > > # - Message Passing library (MPI) -- > > # -- > > # MPinc tells the C compiler where to find the Message Passing library > > # header files, MPlib is defined to be the name of the library to be > > # used. The variable MPdir is only used for defining MPinc and MPlib. > > # > > MPdir= /usr/local/mpi > > MPinc= -I$(MPdir)/include > > MPlib= $(MPdir)/lib/libmpich.a > > > > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users > -- Eric Thibodeau Neural Bucket Solutions Inc. T. (514) 736-1436 C. (514) 710-0517
