[Ns-developers] waf error switching back and forth between debug and optimized mode

[Andrey Mazo]

On Fri, 23 Apr 2010 15:45:36 +0400, Gustavo Carneiro <gjcarneiro at gmail.com> wrote:

> Some people may have seen this error switching back and forth between debug
> and optimized mode:
>
> [...]
>   File
> "/home/sitme/repos/ns-3-sitme/.waf-1.5.13-4340ef810f7db5d61c618fdf96cb5695/wafadmin/Node.py",
> line 125, in find_or_declare
>     self.__class__.bld.rescan(parent)
>   File
> "/home/sitme/repos/ns-3-sitme/.waf-1.5.13-4340ef810f7db5d61c618fdf96cb5695/wafadmin/Build.py",
> line 322, in rescan
>     if node.id in dct:
> TypeError: argument of type 'int' is not iterable
This is bug 855 [1].

> This appears to be fixed in the latest waf, 1.5.16.
>
> I know it's late in the release process, but I have tested locally waf
> 1.5.16 (you need to drop the new waf and also apply the attached patch), and
> it seems to  work fine and fix the problem.  Therefore, I would like to
> upgrade waf before ns 3.8.  Is it ok?
The attached patch isn't required with the latest revision of waf.
If you're anyway going to apply a workaround, it's also possible to make it one-liner:
- sys.path.insert(0, os.path.abspath('waf-tools'))
+ sys.path.append(os.path.abspath('waf-tools'))


[1] http://www.nsnam.org/bugzilla/show_bug.cgi?id=855

-- 
Andrey Mazo.