Bugzilla – Bug 1330
waf doesn't set executable flag on libraries after installation
Last modified: 2012-02-13 13:16:23 UTC
When compiled, executable flag on libraries is set nicely, but waf doesn't set executable flag on libs after installation. I can (and presently do) hack around that, but it would be better to fix it.
It seems that the WAF 1.6.10 upgrade fixed it, in ns-3-dev. Can you check?
Unfortunately it's not fixed. It does work with ns-3-dev, yes, but not with release. To test, I changed VERSION file from 3-dev to 3.14 and got $ ls -l lib/libns3-core.so* lrwxrwxrwx. 1 vedranm vedranm 19 Dec 31 01:00 lib/libns3-core.so -> libns3-core.so.3.14 lrwxrwxrwx. 1 vedranm vedranm 19 Dec 31 01:00 lib/libns3-core.so.3 -> libns3-core.so.3.14 -rw-r--r--. 1 vedranm vedranm 4238832 Dec 31 00:58 lib/libns3-core.so.3.14 However there is an improvement regarding bug 1327. I will post the comment there.
It sounds like a bug in WAF, so I filed a bug report: http://code.google.com/p/waf/issues/detail?id=1097
WAF upgraded, the bug appears to be gone: changeset: 7705:f1c54b0cc754 tag: tip user: Gustavo J. A. M. Carneiro <gjc@inescporto.pt> date: Mon Feb 13 18:15:22 2012 +0000 summary: Upgrade WAF from 1.6.10 to 1.6.11