Hi, I didn't quite understand what this means.. So I do the ../configure in each of the folders for the different architectures and then run make once from the main folder directly? Subramanya Sadasiva
"But memory eventually fades. Turbulences damp out, internal strains yield to plastic flow, concentration inhomogeneities diffuse to uniformity. Systems tend to subside to very simple states,independent of their specific history." Herbert Callen . Thermodynamics and an Introduction to Thermostatics. ----- Original Message ----- From: "Jed Brown" <[email protected]> To: "Roy Stogner" <[email protected]>, "Subramanya Gautam Sadasiva" <[email protected]> Cc: "libmesh-users" <[email protected]> Sent: Monday, March 4, 2013 12:30:40 PM Subject: Re: [Libmesh-users] Multiple Petsc Builds Roy Stogner <[email protected]> writes: > On Mon, 4 Mar 2013, Subramanya Gautam Sadasiva wrote: > >> I'd like to know if I can change the arch of petsc that I am using >> without going through ./configure again. Can I just change the >> make.common file and use other arches of petsc? > > There have been reports of people doing something like this > successfully in the past, but I would strongly recommend against it. > It's easy to slightly change the PETSc ABI via their configuration > options, and it's hard to debug ABI incompatibilities unless you can > catch them at compile time. I recommend doing out-of-source builds. For example libmesh/build-arch1$ ../configure PETSC_ARCH=arch1 libmesh/build-arch2$ ../configure PETSC_ARCH=arch2 Then you can easily switch without needing to reconfigure and recompile all of libmesh. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
