Bug 323 – waf --valgrind doesn't check for valgrind first

Bug 323 - waf --valgrind doesn't check for valgrind first


Summary:	waf --valgrind doesn't check for valgrind first

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	build system
Version:	ns-3-dev
Hardware:	All All

Importance:	P1 enhancement
Assigned To:	Gustavo J. A. M. Carneiro

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-09-08 14:58 UTC by Rajib Bhattacharjea
Modified:	2009-01-24 13:09 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

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

"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.