On Nov 28, 2012, at 2:04 PM, "Paul T. Bauman" <ptbau...@gmail.com> wrote: >> On Wed, Nov 28, 2012 at 1:56 PM, Kirk, Benjamin (JSC-EG311) >> <benjamin.kir...@nasa.gov> wrote: >> To avoid yet-another-method proliferation, my preferred method for handling >> this would be >> >> $ ./configure libmesh_CXXFLAGS="-g -whatever" >> >> and then use the standard opt, dbg, devel as is. This is what I do when I >> want to add -g to the opt flags for use in e.g. intel's VTune >> > Maybe I'm missing something, but the gprof-style flags are compiler dependent > (see compiler.m4, PROFILING_FLAGS), so it'd be nice to have those taken care > of automatically. Thus, it seems as though METHOD=prof may still be useful?
If at all possible I'd rather treat that as --enable-gprof and add the flags to the existing dbg, devel, opt flags - especially if we are going to go with the requested 'multiple mode' support (see libmesh.automake - I've done away with the top-level Make.common.method entirely). Now, if that is no longer a desirable feature, I'll scream really loud because I've wasted a few days, but after that I'll probably capitulate. -Ben ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: INSIGHTS What's next for parallel hardware, programming and related areas? Interviews and blogs by thought leaders keep you ahead of the curve. http://goparallel.sourceforge.net _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
