Re: [OMPI devel] VT in trunk + how to disable

I don't mind enabled by default - however, with a big caveat that we fix the build system issues. With that proviso, "on" by default is fine with me. On 2/5/08 9:00 AM, "Andreas Knüpfer" wrote: > Hi Josh, hi everybody, > > we'd like to have VampirTrace enabled

Re: [OMPI devel] VT in trunk + how to disable

Hi Josh, hi everybody, we'd like to have VampirTrace enabled by default -- well, of course we do ;) Our main reason is the potential users: As soon as they want to use our tool they want to use it with the same configuration as the default Open MPI installation. Making the administrator

Re: [OMPI devel] VT in trunk + how to disable

I think my position is about the same as Terry's. I also think we have a precedent for building everything that is possible and letting the user choose at run-time what they want to do. My $0.02 is that it's easier to tell random users (and customers!) "yes, OMPI should have built that

Re: [OMPI devel] VT in trunk + how to disable

Should the default be to *disable* vampirtrace? I mention this since, I assume, most people do not depend on this tool for every Open MPI install. Meaning that Open MPI does not require this integration for correct MPI functionality unlike something like ROMIO [example of opt-out