ATTN: Regression runners: Versioned toolsets renaming
The following renaming just took place in the CVS: como-win32-4.3.3-vc7.1-tools.jam -> como-4_3_3-vc7-tools.jam como-win32-4.3.3-vc7-tools.jam -> como-4_3_3-vc7_1-tools.jam borland-5.5.1-tools.jam -> borland-5_5_1-tools.jam borland-5.6.4-tools.jam -> borland-5_6_4-tools.jam cw-8.3-tools.jam -> cw-8_3-tools.jam cw-9.2-tools.jam -> cw-9_2-tools.jam cw-9.3-tools.jam -> cw-9_3-tools.jam intel-win32-7.1-vc6-stlport-4.5.3-tools.jam -> iw-7_1-vc6-stlp-4_5_3-tools.jam intel-win32-7.1-vc6-tools.jam -> iw-7_1-vc6-tools.jam intel-win32-8.0-tools.jam -> intel-win32-8_0-tools.jam intel-win32-8.1-tools.jam -> intel-win32-8_1-tools.jam mingw-3.3.1-tools.jam -> mingw-3_3_1-tools.jam mingw-3.4.1-tools.jam -> mingw-3_4_1-tools.jam mingw-3.4.2-tools.jam -> mingw-3_4_2-tools.jam vc7.1-stlport-tools.jam -> vc-7_1-stlport-tools.jam vc7.1-tools.jam -> vc-7_1-tools.jam vc8.0-tools.jam -> vc-8_0-tools.jam vc8.0-x86_amd64-tools.jam -> vc-8_0-x86_amd64-tools.jam If you are running regressions with any of these toolsets, please adjust your scripts to use the new names. "boost-base.jam", docs, and failures markup files has been updated accordingly. Note that the latter will cause a temporary disturbance in the regression reports; things should return back to normal as soon as all runners upload updated results. -- Aleksey Gurtovoy MetaCommunications Engineering
Angus Leeming writes:
Aleksey Gurtovoy wrote:
The following renaming just took place in the CVS:
como-win32-4.3.3-vc7.1-tools.jam -> como-4_3_3-vc7-tools.jam como-win32-4.3.3-vc7-tools.jam -> como-4_3_3-vc7_1-tools.jam
Is this correct? ...vc7.1 -> ...vc7 ...vc7 -> ...vc7_1
Nope, should be the other way around; sorry! The actual toolsets get this correctly, of course. -- Aleksey Gurtovoy MetaCommunications Engineering
I'm only running regression.py which doesn't directly name the jam files...and I'm getting these errors......... ============================================= C:\Projects\boost\tools/build/v1\allyourbase.jam:629: in C++ rule C++-action unknown in module C:\Projects\boost\tools/build/v1\allyourbase.jam:1096: in Object C:\Projects\boost\tools/build/v1\allyourbase.jam:1161: in Objects C:\Projects\boost\tools/build/v1\boost-base.jam:112: in executable-file C:\Projects\boost\tools/build/v1\testing.jam:325: in run-test C:\Projects\boost\tools/build/v1\testing.jam:248: in build-test C:\Projects\boost\tools/build/v1\boost-base.jam:1945: in subvariant-target C:\Projects\boost\tools/build/v1\boost-base.jam:2033: in main-target C:\Projects\boost\tools/build/v1\boost-base.jam:1354: in declare-local-target C:\Projects\boost\tools/build/v1\testing.jam:64: in boost-test C:\Projects\boost\tools/build/v1\testing.jam:493: in run ..\libs\algorithm\minmax\test\Jamfile:30: in load-jamfiles C:\Projects\boost\tools/build/v1\allyourbase.jam:1714: in SubInclude C:\Projects\boost\tools/build/v1\allyourbase.jam:1306: in subinclude Jamfile:18: in load-jamfiles C:\Projects\boost\tools\build\v1\bootstrap.jam:21: in boost-build C:\Projects\boost\boost-build.jam:16: in module scope ============================================================================ At Sunday 2004-10-10 11:53, you wrote:
The following renaming just took place in the CVS:
como-win32-4.3.3-vc7.1-tools.jam -> como-4_3_3-vc7-tools.jam como-win32-4.3.3-vc7-tools.jam -> como-4_3_3-vc7_1-tools.jam borland-5.5.1-tools.jam -> borland-5_5_1-tools.jam borland-5.6.4-tools.jam -> borland-5_6_4-tools.jam cw-8.3-tools.jam -> cw-8_3-tools.jam cw-9.2-tools.jam -> cw-9_2-tools.jam cw-9.3-tools.jam -> cw-9_3-tools.jam intel-win32-7.1-vc6-stlport-4.5.3-tools.jam -> iw-7_1-vc6-stlp-4_5_3-tools.jam intel-win32-7.1-vc6-tools.jam -> iw-7_1-vc6-tools.jam intel-win32-8.0-tools.jam -> intel-win32-8_0-tools.jam intel-win32-8.1-tools.jam -> intel-win32-8_1-tools.jam mingw-3.3.1-tools.jam -> mingw-3_3_1-tools.jam mingw-3.4.1-tools.jam -> mingw-3_4_1-tools.jam mingw-3.4.2-tools.jam -> mingw-3_4_2-tools.jam vc7.1-stlport-tools.jam -> vc-7_1-stlport-tools.jam vc7.1-tools.jam -> vc-7_1-tools.jam vc8.0-tools.jam -> vc-8_0-tools.jam vc8.0-x86_amd64-tools.jam -> vc-8_0-x86_amd64-tools.jam
If you are running regressions with any of these toolsets, please adjust your scripts to use the new names. "boost-base.jam", docs, and failures markup files has been updated accordingly. Note that the latter will cause a temporary disturbance in the regression reports; things should return back to normal as soon as all runners upload updated results.
-- Aleksey Gurtovoy MetaCommunications Engineering
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"
Victor A. Wagner Jr. writes:
I'm only running regression.py which doesn't directly name the jam files...and I'm getting these errors.........
[snip the errors] I guess I should've been clearer: the names of the toolsets you pass to 'regression.py' are directly derived from the names of the *-tools.jam files; e.g.: new .jam file new toolset name ---------------------- ------------------------ mingw-3_4_2-tools.jam mingw-3_4_2 vc_7_1-stlport-tools.jam vc-7_1-stlport vc-7_1-tools.jam vc-7_1 etc. So, if you've been invoking 'regression.py' as, let's say, python regression.py --toolsets=vc7.1 it needs to become python regression.py --toolsets=vc-7_1 HTH, -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy wrote:
The following renaming just took place in the CVS:
[...] The Intel toolsets don't work at all anymore because a) the msvc base toolset is set to a value that is incorrect now ("vc7.1") b) even worse: the Intel compiler options are put together _using_ the msvc base toolset (there is an option that specifies the vc emulation, e.g. "/Qvc7.1") Is there somebody with more bjam experience who can help me? Stefan
Stefan Slapeta writes:
Aleksey Gurtovoy wrote:
The following renaming just took place in the CVS:
[...]
The Intel toolsets don't work at all anymore because
a) the msvc base toolset is set to a value that is incorrect now ("vc7.1")
Hmm, you are setting it yourself through INTEL_BASE_MSVC_TOOLSET though, no? Switching to "vc-7_1" should help.
b) even worse: the Intel compiler options are put together _using_ the msvc base toolset (there is an option that specifies the vc emulation, e.g. "/Qvc7.1")
Fixed in the CVS. -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy wrote:
Hmm, you are setting it yourself through INTEL_BASE_MSVC_TOOLSET though, no? Switching to "vc-7_1" should help.
Oh, of course this should be changed :)
b) even worse: the Intel compiler options are put together _using_ the msvc base toolset (there is an option that specifies the vc emulation, e.g. "/Qvc7.1")
Fixed in the CVS.
Thanks! Stefan
Stefan Slapeta <stefan@slapeta.com> writes:
Aleksey Gurtovoy wrote:
Hmm, you are setting it yourself through INTEL_BASE_MSVC_TOOLSET though, no? Switching to "vc-7_1" should help.
Oh, of course this should be changed :)
b) even worse: the Intel compiler options are put together _using_ the msvc base toolset (there is an option that specifies the vc emulation, e.g. "/Qvc7.1") Fixed in the CVS.
Thanks!
I think we could've changed the filenames only and performed the translation from dots to underscores without requiring users to do it everywhere. Oh well. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
David Abrahams wrote:
I think we could've changed the filenames only and performed the translation from dots to underscores without requiring users to do it everywhere. Oh well.
This would be little confusing for users if left like that in future versions. Better to have it done once, and forget about it :> B.
participants (10)
-
Aleksey Gurtovoy -
Angus Leeming -
Bronek Kozicki -
David Abrahams -
Gennadiy Rozental -
Stefan Slapeta -
Victor A. Wagner Jr.