[1.35.0][tools] Tools build failure
I'm starting to merge trunk changes into branches/release in my working copy. I won't do any commits until at least minimal tests are passing locally. The first merge was the tools directory, Boost.System, and Boost.Filesystem. Current versions of two libraries are needed by some of the tools. While we don't have an explicit test script for tools, I would expect the following to work correctly on Windows, given the working copy is d:\boost\release: d: cd \boost\release\tools\jam/src build copy bin.ntx86\bjam.exe a-directory-in-PATH cd \boost\release\tools bjam >log The bjam build works fine, but the tools build fails. See log file below. Shouldn't this work? Any ideas what's wrong? Note that the following does work OK, and builds process_jam_log.exe: cd \boost\release\tools\regression\build bjam Thanks, --Beman 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). D:/boost/release/tools/build/v2/build\virtual-target.jam:996: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <pregression\build\bin\msvc-8.0\release\link-static\threading-multi>tiny_xml.obj error: previous virtual target { msvc%msvc.compile.c++-tiny_xml.obj.OBJ { detail/tiny_xml.cpp.CPP } } error: created from regression/build/compiler_status error: another virtual target { msvc%msvc.compile.c++-tiny_xml.obj.OBJ { detail/tiny_xml.cpp.CPP } } error: created from regression/build/process_jam_log error: added properties: <define>_CRT_SECURE_NO_WARNINGS error: removed properties: none D:/boost/release/tools/build/v2/build\virtual-target.jam:459: in actualize-no-scanner from module object(file-target)@791 D:/boost/release/tools/build/v2/build\virtual-target.jam:111: in object(file-target)@791.actualize from module object(file-target)@791 D:/boost/release/tools/build/v2/build\virtual-target.jam:743: in actualize-source-type from module object(action)@796 D:/boost/release/tools/build/v2/build\virtual-target.jam:764: in actualize-sources from module object(action)@796 D:/boost/release/tools/build/v2/build\virtual-target.jam:709: in object(action)@796.actualize from module object(action)@796 D:/boost/release/tools/build/v2/build\virtual-target.jam:274: in actualize-action from module object(file-target)@797 D:/boost/release/tools/build/v2/build\virtual-target.jam:467: in actualize-no-scanner from module object(file-target)@797 D:/boost/release/tools/build/v2/build\virtual-target.jam:111: in object(file-target)@797.actualize from module object(file-target)@797 D:/boost/release/tools/build/v2/build\virtual-target.jam:832: in actualize-source-type from module object(non-scanning-action)@1180 D:/boost/release/tools/build/v2/build\virtual-target.jam:764: in actualize-sources from module object(non-scanning-action)@1180 D:/boost/release/tools/build/v2/build\virtual-target.jam:709: in object(non-scanning-action)@1180.actualize from module object(non-scanning-action)@1180 D:/boost/release/tools/build/v2/build\virtual-target.jam:274: in actualize-action from module object(file-target)@1181 D:/boost/release/tools/build/v2/build\virtual-target.jam:467: in actualize-no-scanner from module object(file-target)@1181 D:/boost/release/tools/build/v2/build\virtual-target.jam:111: in object(file-target)@1181.actualize from module object(file-target)@1181 D:/boost/release/tools/build/v2\build-system.jam:488: in load from module build-system D:\boost\release\tools\build\v2/kernel\modules.jam:261: in import from module modules D:\boost\release\tools\build\v2/kernel/bootstrap.jam:132: in boost-build from module D:\boost\release\boost-build.jam:9: in module scope from module
Beman Dawes wrote:
I'm starting to merge trunk changes into branches/release in my working copy. I won't do any commits until at least minimal tests are passing locally.
The first merge was the tools directory, Boost.System, and Boost.Filesystem. Current versions of two libraries are needed by some of the tools.
Minor note... Please merge a released version of bjam to the release, instead of the one in trunk. Hence "tags/tools/jam/Boost_Jam_3_1_15". Not that it will affect the error.
While we don't have an explicit test script for tools, I would expect the following to work correctly on Windows, given the working copy is d:\boost\release:
d: cd \boost\release\tools\jam/src build copy bin.ntx86\bjam.exe a-directory-in-PATH
cd \boost\release\tools bjam >log
Yea, that should work...
error: Duplicate name of actual target: <pregression\build\bin\msvc-8.0\release\link-static\threading-multi>tiny_xml.obj error: previous virtual target { msvc%msvc.compile.c++-tiny_xml.obj.OBJ { detail/tiny_xml.cpp.CPP } } error: created from regression/build/compiler_status error: another virtual target { msvc%msvc.compile.c++-tiny_xml.obj.OBJ { detail/tiny_xml.cpp.CPP } } error: created from regression/build/process_jam_log error: added properties: <define>_CRT_SECURE_NO_WARNINGS error: removed properties: none
Hm, I think I know the problem... Yep, fixed now <http://svn.boost.org/trac/boost/changeset/41110>. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Rene Rivera wrote:
Beman Dawes wrote:
I'm starting to merge trunk changes into branches/release in my working copy. I won't do any commits until at least minimal tests are passing locally.
The first merge was the tools directory, Boost.System, and Boost.Filesystem. Current versions of two libraries are needed by some of the tools.
Minor note... Please merge a released version of bjam to the release, instead of the one in trunk. Hence "tags/tools/jam/Boost_Jam_3_1_15". Not that it will affect the error.
OK, will do.
While we don't have an explicit test script for tools, I would expect the following to work correctly on Windows, given the working copy is d:\boost\release:
d: cd \boost\release\tools\jam/src build copy bin.ntx86\bjam.exe a-directory-in-PATH
cd \boost\release\tools bjam >log
Yea, that should work...
error: Duplicate name of actual target: <pregression\build\bin\msvc-8.0\release\link-static\threading-multi>tiny_xml.obj error: previous virtual target { msvc%msvc.compile.c++-tiny_xml.obj.OBJ { detail/tiny_xml.cpp.CPP } } error: created from regression/build/compiler_status error: another virtual target { msvc%msvc.compile.c++-tiny_xml.obj.OBJ { detail/tiny_xml.cpp.CPP } } error: created from regression/build/process_jam_log error: added properties: <define>_CRT_SECURE_NO_WARNINGS error: removed properties: none
Hm, I think I know the problem... Yep, fixed now <http://svn.boost.org/trac/boost/changeset/41110>.
Thanks for the fast response! --Beman
Beman Dawes wrote:
Rene Rivera wrote:
Hm, I think I know the problem... Yep, fixed now <http://svn.boost.org/trac/boost/changeset/41110>.
On Linux, the tiny_xml.cpp compile is now failing because no -I is given, so no boost headers are found:-( --Beman
Beman Dawes wrote:
Beman Dawes wrote:
Rene Rivera wrote:
Hm, I think I know the problem... Yep, fixed now <http://svn.boost.org/trac/boost/changeset/41110>.
On Linux, the tiny_xml.cpp compile is now failing because no -I is given, so no boost headers are found:-(
Weird how the build worked locally when I first tested the change but doesn't work now :-\ I have a fix for it locally. But now I'm running into an entirely different problem of PJL trying to link to both the static and dynamic versions of Boost.System at the same time... not a good thing. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Rene Rivera wrote:
Beman Dawes wrote:
Beman Dawes wrote:
Rene Rivera wrote:
Hm, I think I know the problem... Yep, fixed now <http://svn.boost.org/trac/boost/changeset/41110>. On Linux, the tiny_xml.cpp compile is now failing because no -I is given, so no boost headers are found:-(
Weird how the build worked locally when I first tested the change but doesn't work now :-\ I have a fix for it locally. But now I'm running into an entirely different problem of PJL trying to link to both the static and dynamic versions of Boost.System at the same time... not a good thing.
On Windows, this is now failing with the same missing -I problem: cd boost-root/tools/regression/build bjam It was working earlier today, before 41110. HTH, --Beman
Rene Rivera wrote:
But now I'm running into an entirely different problem of PJL trying to link to both the static and dynamic versions of Boost.System at the same time... not a good thing.
Fixed with <http://svn.boost.org/trac/boost/changeset/41118> and <http://svn.boost.org/trac/boost/changeset/41119>. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Rene Rivera wrote:
Rene Rivera wrote:
But now I'm running into an entirely different problem of PJL trying to link to both the static and dynamic versions of Boost.System at the same time... not a good thing.
Fixed with <http://svn.boost.org/trac/boost/changeset/41118> and <http://svn.boost.org/trac/boost/changeset/41119>.
Works for Windows. I'll try Linux later. Thanks, --Beman
participants (2)
-
Beman Dawes -
Rene Rivera