[bjam] can't build boost (latest version from SVN)
Hi all, After getting latest boost from svn (and latest bjam), can't build it. I've attached the error. Command line: bjam toolset=msvc (note: simple 'bjam' generates the same error) Best, John -- http://John.Torjo.com -- C++ expert ... call me only if you want things done right warning: Graph library does not contain optional GraphML reader. note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to the note: directories containing the Expat headers and libraries, respectively. warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. WARNING: No python installation configured and autoconfiguration failed. See http://www.boost.org/libs/python/doc/building.html for configuration instructions or pass --without-python to suppress this message and silently skip all Boost.Python targets Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (don't panic: this is a strictly optional feature). Skipping build of: ./headers <build>no in common properties Skipping build of: ./headers <build>no in common properties Skipping build of: ./headers <build>no in common properties Skipping build of: ./headers <build>no in common properties Skipping build of: libs/python/build/boost_python <build>no in common properties D:/john/code/latest_boost/tools/build/v2/build\virtual-target.jam:423: in _adjust-name from module object(file-target)@1277 error: <tag>@rulename is present but is not the only <tag> feature D:/john/code/latest_boost/tools/build/v2/build\virtual-target.jam:215: in abstract-file-target.__init__ from module object(file-target)@1277 D:/john/code/latest_boost/tools/build/v2/build\virtual-target.jam:531: in object(file-target)@1277.__init__ from module object(file-target)@1277 D:/john/code/latest_boost/tools/build/v2/kernel\class.jam:93: in class.new from module class D:/john/code/latest_boost/tools/build/v2/build\generators.jam:449: in generated-targets from module object(C-compiling-generator)@22 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:362: in construct-result from module object(C-compiling-generator)@22 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:328: in run-really from module object(C-compiling-generator)@22 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:299: in object(C-compiling-generator)@22.run from module object(C-compiling-generator)@22 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:840: in try-one-generator-really from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:902: in try-one-generator from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:1108: in construct-really from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:1184: in construct from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:914: in generators.construct-types from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:502: in convert-to-consumable-types from module object(linking-generator)@20 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:560: in convert-multiple-sources-to-consumable-types from module object(linking-generator)@20 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:314: in run-really from module object(linking-generator)@20 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:299: in generator.run from module object(linking-generator)@20 D:/john/code/latest_boost/tools/build/v2/tools\builtin.jam:750: in object(linking-generator)@20.run from module object(linking-generator)@20 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:840: in try-one-generator-really from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:902: in try-one-generator from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:1108: in construct-really from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:1184: in generators.construct from module generators D:/john/code/latest_boost/tools/build/v2/tools\builtin.jam:494: in object(lib-generator)@5.run from module object(lib-generator)@5 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:840: in try-one-generator-really from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:902: in try-one-generator from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:1108: in construct-really from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:1184: in generators.construct from module generators D:/john/code/latest_boost/tools/build/v2/build\targets.jam:1402: in construct from module object(typed-target)@290 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:1231: in object(typed-target)@290.generate from module object(typed-target)@290 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:751: in generate-really from module object(main-target)@1258 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:724: in object(main-target)@1258.generate from module object(main-target)@1258 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:255: in object(project-target)@276.generate from module object(project-target)@276 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:874: in targets.generate-from-reference from module targets D:/john/code/latest_boost/tools/build/v2/build\targets.jam:1149: in generate-dependencies from module object(alias-target-class)@75 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:1203: in object(alias-target-class)@75.generate from module object(alias-target-class)@75 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:751: in generate-really from module object(main-target)@355 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:724: in object(main-target)@355.generate from module object(main-target)@355 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:255: in object(project-target)@31.generate from module object(project-target)@31 D:/john/code/latest_boost/tools/build/v2\build-system.jam:414: in load from module build-system D:\john\code\latest_boost\tools\build\v2/kernel\modules.jam:261: in import from module modules D:\john\code\latest_boost\tools\build\v2/kernel/bootstrap.jam:132: in boost-build from module D:\john\code\latest_boost\boost-build.jam:11: in module scope from module
John Torjo wrote:
Hi all,
After getting latest boost from svn (and latest bjam), can't build it. I've attached the error. Command line: bjam toolset=msvc
(note: simple 'bjam' generates the same error)
Can you run 'bjam --debug-building toolset=msvc', and figure which library causes this error? - Volodya
Can you run 'bjam --debug-building toolset=msvc', and figure which library causes this error?
Seems to be boost_thread. Have no idea why. I've attached the output. Best, John
- Volodya
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- http://John.Torjo.com -- C++ expert ... call me only if you want things done right
John Torjo wrote:
Can you run 'bjam --debug-building toolset=msvc', and figure which library causes this error?
Seems to be boost_thread. Have no idea why. I've attached the output.
Well, this indeed seems to be Boost.Thread issue, and from the error message it does not seem to be due to Boost.Build recent changes, but rather from Boost.Thread changes. Can any Boost.Thread developer investigate? - Volodya
Vladimir Prus <ghost <at> cs.msu.su> writes:
Well, this indeed seems to be Boost.Thread issue, and from the error message it does not seem to be due to Boost.Build recent changes, but rather from Boost.Thread changes.
Can any Boost.Thread developer investigate?
I don't get these errors here, with msvc 7.1, 8.0 or 9.0 Anthony
Hi John.
After getting latest boost from svn (and latest bjam), can't build it. I've attached the error.
I've just updated my trunk sandbox and ran 'bjam toolset=msvc' in the boost root folder and everything built fine using msvc 7.1. Tried it using bjam 3.1.16 (1.34.1 boost library release) and the 3.1.17 from the trunk... I'm attaching the --debug-building log I got on my side with bjam 3.1.17 (with renamed folder path to match yours...) The only differences I see is that I use msvc 7.1 and you use msvc 8.0. and that for some reason some paths (related to boost Graph I think) in on your side are displayed using backslashes instead of slashes. Also, you have your Jamroot file set so it uses the complete build type by default... Any other local changes on your side? Hope this helps... Best regards, Jurko Gospodnetić
I've just updated my trunk sandbox and ran 'bjam toolset=msvc' in the boost root folder and everything built fine using msvc 7.1. Tried it using bjam 3.1.16 (1.34.1 boost library release) and the 3.1.17 from the trunk...
I'm attaching the --debug-building log I got on my side with bjam 3.1.17 (with renamed folder path to match yours...)
The only differences I see is that I use msvc 7.1 and you use msvc 8.0. and that for some reason some paths (related to boost Graph I think) in on your side are displayed using backslashes instead of slashes.
Also, you have your Jamroot file set so it uses the complete build type by default... Any other local changes on your side?
Note that my Jamroot is the latest from SVN. Best, John
Hope this helps...
Best regards, Jurko Gospodnetić
------------------------------------------------------------------------
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- http://John.Torjo.com -- C++ expert ... call me only if you want things done right
Hi John.
Note that my Jamroot is the latest from SVN.
I am not so sure. The last changed revision on the trunk is 41734 and in that one the default build-type is minimal. The one on the release branch does not have the build-type option at all and is coded to always work as if it has build-type set to minimal. You either added the --build-type=complete command-line parameter to your command-line (that's what I did), have some magic in your configuration files or modified the Jamroot file... otherwise your build would not produce all those variants listed in your error log. Best regards, Jurko Gospodnetić
participants (4)
-
Anthony Williams -
John Torjo -
Jurko Gospodnetić -
Vladimir Prus