|
Bugzilla – Full Text Bug Listing |
| Summary: | waf 1.6.10 upgrade breaks OS X build when Python enabled | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | Tom Henderson <tomh> |
| Component: | build system | Assignee: | Gustavo J. A. M. Carneiro <gjcarneiro> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ns-bugs, tommaso.pecorella |
| Priority: | P5 | ||
| Version: | pre-release | ||
| Hardware: | All | ||
| OS: | All | ||
Well, I removed our copy of the python waf tool, because the upstream version supposedly fixes the bug that the copy was supposed to fix. Something in waf 1.6.10 upgrade breaks this... :-( I found the bug, and filed it: http://code.google.com/p/waf/issues/detail?id=1098 *** Bug 1337 has been marked as a duplicate of this bug. *** This change should fix it (workaround for waf bug). changeset: 7678:a4c56ef461ba tag: tip user: Gustavo J. A. M. Carneiro <gjc@inescporto.pt> date: Sun Jan 08 16:26:02 2012 +0000 summary: Bug 1335 - waf 1.6.10 upgrade breaks OS X build when Python enabled |
How to reproduce: Darwin (Snow Leopard) with python 2.6 and 2.7 (machine 'darwin' at UW) ./waf configure --with-python=/opt/local/bin/python2.7 --enable-examples --enable-tests ./waf yields: i686-apple-darwin10-g++-4.2.1: -bundle not allowed with -dynamiclib Waf: Leaving directory `/private/tmp/ns-commits/tests/tmp/ns-3-allinone/ns-3-dev /build' Build failed -> task failed (exit status 1): {task 4322619920: cxxshlib ns3module.cc.5.o -> config_store.so} ['/usr/bin/g++', '-dynamiclib', '-bundle', '-undefined', 'dynamic_lookup', 'src/ config-store/bindings/ns3module.cc.5.o', '-o', '/private/tmp/ns-commits/tests/tm p/ns-3-allinone/ns-3-dev/build/bindings/python/ns/config_store.so', '-L.', '-L.' , '-L.', '-L.', '-L.', '-L.', '-L.', '-L.', '-L.', '-L.', '-L.', '-L.', '-L.', ' -L.', '-L.', '-L.', '-L.', '-L.', '-L.', '-L.', '-L.', '-L.', '-L.', '-L.', '-L. ', '-L.', '-L.', '-L.', '-L.', '-L.', '-L.', '-L.', '-L/opt/local/lib', '-L/opt/ local/lib', '-L/opt/local/lib', '-lns3-aodv', '-lns3-dsdv', '-lns3-mesh', '-lns3 -test', '-lns3-csma-layout', '-lns3-point-to-point-layout', '-lns3-netanim', '-l ns3-olsr', '-lns3-csma', '-lns3-lte', '-lns3-wimax', '-lns3-spectrum', '-lns3-ap plications', '-lns3-virtual-net-device', '-lns3-uan', '-lns3-energy', '-lns3-flo w-monitor', '-lns3-nix-vector-routing', '-lns3-visualizer', '-lns3-internet', '- lns3-bridge', '-lns3-point-to-point', '-lns3-mpi', '-lns3-wifi', '-lns3-propagat ion', '-lns3-mobility', '-lns3-config-store', '-lns3-tools', '-lns3-stats', '-ln s3-topology-read', '-lns3-network', '-lns3-core', '-lxml2', '-lpthread', '-lz', '-liconv', '-lm', '-lsqlite3', '-lpython2.7'] This seems to have been introduced in the past day or two; changeset 7669 ab2af491785a from 30 Dec. does not exhibit the problem.