Turns out that there was a plethora of include file conflicts. The Debian release upgrade from Etch to Lenny/testing did not remove the old MPI implementations (MPICH/LAM) when moving over to PETSc/OpenMPI. As I suspected, this upgrade took care of an odd bug I was having when using PETSc/MPICH that is default on Etch. My code is working great now! Thanks for your help.
Nasser p.s. I'll send an update for the Wiki soon, does anyone know why the LibMesh package was removed from Debian Testing and put in Unstable? Roy Stogner wrote: > > On Mon, 14 Jul 2008, Nasser Mohieddin Abukhdeir wrote: > >> ./configure --with-cxx=mpicxx.openmpi --with-cc=mpicc.openmpi >> --with-f77=mpif77.openmpi -with-CC=mpiCC.openmpi >> >> [EMAIL PROTECTED]:> mpiexec -np 1 ./main-opt > > I'm not a Debian user and I have no idea what the real problem is, but > this stuck out at me: If you're postfixing mpicc, etc. with > ".openmpi", presumably to avoid LAM/OpenMPI conflicts, do you need to > be running "mpiexec.openmpi" as well? > > The only other possibility I can think of is that there's a conflict > with include files, getting the wrong mpi.h compiled into your libMesh > install. > --- > Roy -- Nasser Mohieddin Abukhdeir Graduate Student (Materials Modeling Research Group) McGill University - Department of Chemical Engineering http://webpages.mcgill.ca/students/nabukh/web/ http://mmrg.chemeng.mcgill.ca/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
