Josh Hursey wrote:
> 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 functionality which is 3rd
> So I would suggest to the group that vampirtrace be an opt-in
> What do others think?
I am not completely against disabling it as a default. However, once it
builds consistently having it enabled by default shouldn't really cause
any problems for those not directly using it (well outside of more time
to compile). I imagine changing the default probably would help ORTE
move forward but then I wonder if we will run into issues of the vampire
stuff not being able to resolve their issues because of ORTE problems
put back to the trunk.
> -- Josh
> On Jan 28, 2008, at 9:59 AM, Andreas Knüpfer wrote:
>> Hi everybody,
>> the vampirtrace integration arrived at the trunk today. There seems
>> to be one
>> issue already, but we'll fix this asap.
>> As a general hint, this is how to completely disable anything we
>> configure --enable-contrib-no-build=vt ...
>> Then again, we'd like to see all the issues you may encounter and
>> fix them.
>> Best regards, Andreas
>> Dipl. Math. Andreas Knuepfer,
>> Center for Information Services and
>> High Performance Computing (ZIH), TU Dresden,
>> Willersbau A114, Zellescher Weg 12, 01062 Dresden
>> phone +49-351-463-38323, fax +49-351-463-37773
>> devel mailing list
> devel mailing list