|
Bugzilla – Full Text Bug Listing |
| Summary: | Bake don't use the current interpretter when building | ||
|---|---|---|---|
| Product: | bake | Reporter: | Mathias Ettinger <mettinger> |
| Component: | bake | Assignee: | Daniel Camara <daniel.camara> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ns-bugs, tomh |
| Priority: | P3 | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | Patch that solved the issue | ||
+1, moving to last call Fixed in changeset 395:c0a5ec615276 Fixed in changeset 394:6dfa00ee748f |
Created attachment 3000 [details] Patch that solved the issue Bake make the strong assumption that `python` is the binary used to launch it. This is usually the case but restrict usages such as $ python2 bake.py deploy where /usr/bin/python is a simlink to the Python 3 interpretter. Thus not propagating my choice of using Python 2 to the waf calls when building NS-3. Instead, builders such as WafModuleBuild or PythonModuleBuild should use `sys.executable` to reflect the choice of the user rather than arbitrarily forcing it. Please find attached a patch applying such changes.