Bug 323

Summary:	waf --valgrind doesn't check for valgrind first
Product:	ns-3	Reporter:	Rajib Bhattacharjea <raj.b>
Component:	build system	Assignee:	Gustavo J. A. M. Carneiro <gjcarneiro>
Status:	RESOLVED FIXED
Severity:	enhancement	CC:	craigdo, ns-bugs
Priority:	P1
Version:	ns-3-dev
Hardware:	All
OS:	All

Description Rajib Bhattacharjea 2008-09-08 14:58:42 EDT

"waf --valgrind stuff" produces a cryptic python error along the lines of "file not found" when valgrind isn't present on the system.  It would be nice if waf configure could check for valgrind, and in the case that it isn't found, "waf --valgrind stuff" could produce an output message like "--valgrind option is disabled since valgrind was not found on this system", and then either fail, or run "stuff" anyway without valgrind.

I suspect --doxygen is the same way, but can't verify, and that is a separate bug report anyway.