yes On Tue, Apr 29, 2008 at 7:28 AM, Roy Stogner <[EMAIL PROTECTED]> wrote: > > On Tue, 29 Apr 2008, Nasser Mohieddin Abukhdeir wrote: > > > this didn't seem to make it the first time > > We got it. > > Should we add this to the libMesh installation wiki page? We've got > some libMesh-on-Debian instructions there, but they may be getting a > bit outdated. > --- > Roy > > > > > Nasser Mohieddin Abukhdeir wrote: > >> Hi: > >> I agonized a little today getting LibMesh working on one of my > >> group's computational servers so I decided to document the > >> installation process: > >> > >> -----Installation on Debian Lenny/Testing----- > >> > >>> aptitude install libmesh0.6.1 libmesh0.6.1-dev > >> > >> Yes, its that easy, but not so fast... > >> > >> > >> ----Installation on Debian Etch/Stable----- > >> > >> 1) I used the latest version of LibMesh (0.6.2) > >> 2) Installing the package petsc-dev takes care of installing MPICH for > >> you > >> > >>> aptitude install petsc-dev > >> > >> Edit the file /etc/mpich/machines.linux to describe your network > >> topology, I just want to use my SMP machine, so I added this line: > >> > >> localhost:8 > >> > >> where the ":8" reflects the number of processors my system has. > >> > >> 3) Unfortunately it does not install rsh which is required my MPICH: > >> > >>> aptitude install rsh-server rsh-client > >> > >> 4) Create a file ~/.rhosts and add a line: > >> > >> localhost USERNAME > >> > >> where you substitute your user name in, you also might have to add > >> "localhost" to your /etc/hosts.allow file for this to work. At this > >> point you should be able to run "tstmachines.mpich" to verify that MPI > >> is working > >> > >> 5) Unpack the LibMesh tarball and do the following (depending on your > >> shell): > >> > >>> export PETSC_ARCH="linux-gnu-c-opt" > >>> export PETSC_DIR="/usr/lib/petscdir/2.3.2/" > >>> ./configure --with-mpi=/usr/lib/mpich --with-cxx=mpicxx.mpich > >> --with-cc=mpicc.mpich --with-f77=mpif77.mpich -with-CC=mpiCC.mpich > >> > >> This took me a while to figure out, but you need to make sure LibMesh > >> knows you are using MPICH, because without the first option it will be > >> configured for LAM-MPI. The other options are intuitive, except you > >> need to use the suffix ".mpich" on all of the compilers so that you do > >> not end up using the LAM wrapper version > >> > >> 6) Compile and test (if you have multiple processors use the -j option > >> to let make know) > >> > >>> make -j 8 > >>> cd examples/ex9 > >>> mpirun -np 8 ./ex9-opt > >> > >> Hopefully I didn't miss anything. > >> > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > > Don't miss this year's exciting event. There's still time to save $100. > > Use priority code J8TL2D2. > > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > > _______________________________________________ > > Libmesh-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/libmesh-users > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Libmesh-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-users >
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
