Can't build in status?
I can't seem to get building anything in the status directory working, I'm using: bjam --dump-tests msvc-14.0 -n But any combination of arguments seems to fail, the failures are: M:/data/boost/boost/tools/build/src/build\property.jam:743: in class@property-map.find from module object(property-map)@236 error: Ambiguous key M:/data/boost/boost/tools/build/src/build\type.jam:333: in generated-target-ps from module type M:/data/boost/boost/tools/build/src/build\type.jam:270: in type.generated-target-suffix from module type M:/data/boost/boost/tools/build/src/build\virtual-target.jam:509: in virtual-target.add-prefix-and-suffix from module virtual-target M:/data/boost/boost/tools/build/src/build\virtual-target.jam:468: in _adjust-name from module object(file-target)@149078 M:/data/boost/boost/tools/build/src/build\virtual-target.jam:253: in abstract-file-target.__init__ from module object(file-target)@149078 M:/data/boost/boost/tools/build/src/build\virtual-target.jam:561: in class@file-target.__init__ from module object(file-target)@149078 M:/data/boost/boost/tools/build/src/kernel\class.jam:90: in class.new from module class M:/data/boost/boost/tools/build/src/build\generators.jam:558: in generator.generated-targets from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\builtin.jam:886: in linking-generator.generated-targets from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\unix.jam:67: in generated-targets from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/build\generators.jam:459: in construct-result from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/build\generators.jam:412: in run-really from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/build\generators.jam:386: in generator.run from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\builtin.jam:801: in linking-generator.run from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\unix.jam:41: in unix-linking-generator.run from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/tools\gcc.jam:692: in class@gcc-linking-generator.run from module object(gcc-linking-generator)@149065 M:/data/boost/boost/tools/build/src/build\generators.jam:994: in try-one-generator-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1056: in try-one-generator from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1294: in construct-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1378: in generators.construct from module generators M:/data/boost/boost/tools/build/src/tools\python.jam:1160: in class@python-test-generator.run from module object(python-test-generator)@244 M:/data/boost/boost/tools/build/src/build\generators.jam:994: in try-one-generator-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1056: in try-one-generator from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1294: in construct-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1378: in construct from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1069: in generators.construct-types from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:609: in convert-to-consumable-types from module object(generator)@245 M:/data/boost/boost/tools/build/src/build\generators.jam:405: in run-really from module object(generator)@245 M:/data/boost/boost/tools/build/src/build\generators.jam:386: in class@generator.run from module object(generator)@245 M:/data/boost/boost/tools/build/src/build\generators.jam:994: in try-one-generator-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1056: in try-one-generator from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1294: in construct-really from module generators M:/data/boost/boost/tools/build/src/build\generators.jam:1378: in generators.construct from module generators M:/data/boost/boost/tools/build/src/build\targets.jam:1553: in construct from module object(typed-target)@19839 M:/data/boost/boost/tools/build/src/build\targets.jam:1353: in class@basic-target.generate from module object(typed-target)@19839 M:/data/boost/boost/tools/build/src/build\targets.jam:774: in generate-really from module object(main-target)@148055 M:/data/boost/boost/tools/build/src/build\targets.jam:746: in class@main-target.generate from module object(main-target)@148055 M:/data/boost/boost/tools/build/src/build\targets.jam:895: in targets.generate-from-reference from module targets M:/data/boost/boost/tools/build/src/build\targets.jam:1266: in generate-dependencies from module object(alias-target-class)@19840 M:/data/boost/boost/tools/build/src/build\targets.jam:1323: in class@basic-target.generate from module object(alias-target-class)@19840 M:/data/boost/boost/tools/build/src/build\targets.jam:774: in generate-really from module object(main-target)@148056 M:/data/boost/boost/tools/build/src/build\targets.jam:746: in class@main-target.generate from module object(main-target)@148056 M:/data/boost/boost/tools/build/src/build\targets.jam:272: in class@project-target.generate from module object(project-target)@19754 M:/data/boost/boost/tools/build/src/build\targets.jam:272: in class@project-target.generate from module object(project-target)@2060 M:/data/boost/boost/tools/build/src\build-system.jam:710: in load from module build-system M:\data\boost\boost\tools\build\src/kernel\modules.jam:295: in import from module modules M:\data\boost\boost\tools\build\src/kernel/bootstrap.jam:139: in boost-build from module M:\data\boost\boost\boost-build.jam:17: in module scope from module Anyone any ideas? Thanks, John.
AMDG On 02/26/2016 12:39 PM, John Maddock wrote:
I can't seem to get building anything in the status directory working, I'm using:
bjam --dump-tests msvc-14.0 -n
But any combination of arguments seems to fail, the failures are:
M:/data/boost/boost/tools/build/src/build\property.jam:743: in class@property-map.find from module object(property-map)@236 error: Ambiguous key
I can't reproduce this. In Christ, Steven Watanabe
AMDG On 02/26/2016 12:39 PM, John Maddock wrote:
I can't seem to get building anything in the status directory working, I'm using:
bjam --dump-tests msvc-14.0 -n
But any combination of arguments seems to fail, the failures are:
M:/data/boost/boost/tools/build/src/build\property.jam:743: in class@property-map.find from module object(property-map)@236 error: Ambiguous key
Do you have everything up-to-date?
Here's what I get:
$ git pull
...
$ git submodule update
...
$ git log
commit 19f44d56ae9aad8458c70570ee818610ee0499f7
Author: Automated Commit
On 26/02/2016 20:06, Steven Watanabe wrote:
AMDG
On 02/26/2016 12:39 PM, John Maddock wrote:
I can't seem to get building anything in the status directory working, I'm using:
bjam --dump-tests msvc-14.0 -n
But any combination of arguments seems to fail, the failures are:
M:/data/boost/boost/tools/build/src/build\property.jam:743: in class@property-map.find from module object(property-map)@236 error: Ambiguous key
Do you have everything up-to-date?
Yes, I've checked out a fresh copy of master and the issue is still there - tracked it down to: using python ; In my user-config.jam. There is only one python.exe in my path so I'm stumped? Thanks, John.
AMDG On 02/27/2016 06:12 AM, John Maddock wrote:
On 26/02/2016 20:06, Steven Watanabe wrote:
On 02/26/2016 12:39 PM, John Maddock wrote:
I can't seem to get building anything in the status directory working, I'm using:
bjam --dump-tests msvc-14.0 -n
But any combination of arguments seems to fail, the failures are:
M:/data/boost/boost/tools/build/src/build\property.jam:743: in class@property-map.find from module object(property-map)@236 error: Ambiguous key
Do you have everything up-to-date?
Yes, I've checked out a fresh copy of master and the issue is still there - tracked it down to:
using python ;
In my user-config.jam. There is only one python.exe in my path so I'm stumped?
Is python initialized more than once, somehow? Otherwise, I'd like see the values of $($(best)) and $($(self.all-flags)). Perhaps now would be a good time to start promoting my debugger for Jam. After building b2 from the debug branch: $ b2 -dconsole (b2db) break property.jam:743 Breakpoint 1 set at property.jam:743 (b2db) run --dump-tests msvc-14.0 -n ... (b2db) print $($(best)) (b2db) print $($(self.all-flags)) In Christ, Steven Watanabe
Is python initialized more than once, somehow? Otherwise, I'd like see the values of $($(best)) and $($(self.all-flags)).
Perhaps now would be a good time to start promoting my debugger for Jam. After building b2 from the debug branch: $ b2 -dconsole (b2db) break property.jam:743 Breakpoint 1 set at property.jam:743 (b2db) run --dump-tests msvc-14.0 -n ... (b2db) print $($(best)) (b2db) print $($(self.all-flags))
Breakpoint 1, class@property-map.find ( object(property-set)@149526 ) at M:/data/boost/boost-master/tools/build/src/build\property.jam:743 743 errors.error "Ambiguous key $(properties:J= :E=)" ; (b2db) print $($(best)) (b2db) print $($(self.all-flags)) <.pyd> <python>2.5 <target-os>windows <.pyd> <python>2.5 <target-os>windows (b2db) Note that I actually have: $ python --version Python 2.7.10
AMDG On 02/27/2016 09:57 AM, John Maddock wrote:
<snip> Breakpoint 1, class@property-map.find ( object(property-set)@149526 ) at M:/data/boost/boost-master/tools/build/src/build\property.jam:743 743 errors.error "Ambiguous key $(properties:J= :E=)" ; (b2db) print $($(best))
My mistake. It should be $(best), but the next one shows everything I need to see anyway.
(b2db) print $($(self.all-flags)) <.pyd> <python>2.5 <target-os>windows <.pyd> <python>2.5 <target-os>windows (b2db)
That definitely looks like python is getting initialized twice.
Note that I actually have:
$ python --version Python 2.7.10
The 2.5 is probably coming from python.jam:808. If this path is reached, then .configured will not be set, which means that if project-config.jam has if ! [ python.configured ] { using python ; } it will attempt to initialize python a second time. I expect that running with --debug-configuration will show that the python headers and/or libraries are not being found for some reason. In Christ, Steven Watanabe
it will attempt to initialize python a second time.
I expect that running with --debug-configuration will show that the python headers and/or libraries are not being found for some reason.
It seems I had cygwin python in my path, and it wasn't happy with that for some reason, I've changed to adding an explicit path to a windows build, and that seems to work OK. Thanks for your help, John.
AMDG On 02/27/2016 11:22 AM, John Maddock wrote:
it will attempt to initialize python a second time.
I expect that running with --debug-configuration will show that the python headers and/or libraries are not being found for some reason.
It seems I had cygwin python in my path, and it wasn't happy with that for some reason, I've changed to adding an explicit path to a windows build, and that seems to work OK.
I've just committed a fix to avoid causing an impenetrable error in Boost.Build for this. Instead, you'll (probably) get an error about missing headers when attempting to build anything using python. Hopefully, this will make the problem a bit easier to track down next time. In Christ, Steven Watanabe
I've just committed a fix to avoid causing an impenetrable error in Boost.Build for this. Instead, you'll (probably) get an error about missing headers when attempting to build anything using python. Hopefully, this will make the problem a bit easier to track down next time. Thanks! In Christ, Steven Watanabe
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
AMDG On 02/27/2016 09:59 AM, John Maddock wrote:
Is python initialized more than once, somehow?
I see Boost.Python has it's own:
using python ;
in at least 2 Jamfiles, do these conflict?
They aren't supposed to, because they're guarded by [ python.configured ], but it seems that you're hitting a combination of two bugs in python.jam. - Your python installation is not being correctly detected. - Failed configuration leaves python.jam in an invalid state. In Christ, Steven Watanabe
participants (2)
-
John Maddock -
Steven Watanabe