It is still valid, however it is really a minor bug, since it can happen (rarely) using nodejs-dev, which provides non-critical development tool.
Upstream waf 1.5.18 has corrected this, but upstream nodejs, as of 0.2.2, is still using waf 1.5.16. A note for the maintainer (me) : close the bug when nodejs updates its waf copy to >= 1.5.18 ! Jérémy. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
