Dear regression runners, As we are closing in on the release, I'd like to ask everybody to switch from the release branch to tarball testing. If you are currently using "regression.py", the switch is almost trivial: 1) Download the updated "regression.py" from http://www.meta-comm.com/engineering/boost/regression.py 2) Download the archive of your choice: http://www.meta-comm.com/engineering/boost/200411020208/boost_1_32_0.tar.bz2 http://www.meta-comm.com/engineering/boost/200411020208/boost_1_32_0.tar.gz http://www.meta-comm.com/engineering/boost/200411020208/boost_1_32_0.zip 3) Place the script and the archive in the same directory (e.g. the same one you are currently using for tests on the branch) 4) Modify the script command line to include '--local' option: python regression.py --local=<archive name> [<all other options>] For example, python regression.py --local=boost_1_32_0.zip --runner=metacomm --toolsets=msvc,vc7,vc-7_1,cw-8_3 --pjl-toolset=vc-7_1 5) That's it. If you are using "collect_and_upload_logs.py", simply change '--tag=RC_1_32_0" to "--tag=boost_1_32_0". All test results will be uploaded to ftp://fx.meta-comm.com/boost-regression/boost_1_32_0/, picked up by the reporting tools, and displayed in the usual location -- http://www.meta-comm.com/engineering/boost-regression/developer/index.html. Thank you! -- Aleksey Gurtovoy MetaCommunications Engineering
OH, this is more of the bullshit we do because someone once decided to tell all the TESTERS they have to change when a release comes along instead of the developers this is getting to where it's hardly worth the trouble to tell you guys you have something that is NOT ready to release if you don't want my results, I'll gladly stop testing At Tuesday 2004-11-02 03:24, you wrote:
Dear regression runners,
As we are closing in on the release, I'd like to ask everybody to switch from the release branch to tarball testing.
If you are currently using "regression.py", the switch is almost trivial:
1) Download the updated "regression.py" from http://www.meta-comm.com/engineering/boost/regression.py
2) Download the archive of your choice:
http://www.meta-comm.com/engineering/boost/200411020208/boost_1_32_0.tar.bz2
http://www.meta-comm.com/engineering/boost/200411020208/boost_1_32_0.tar.gz http://www.meta-comm.com/engineering/boost/200411020208/boost_1_32_0.zip
3) Place the script and the archive in the same directory (e.g. the same one you are currently using for tests on the branch)
4) Modify the script command line to include '--local' option:
python regression.py --local=<archive name> [<all other options>]
For example,
python regression.py --local=boost_1_32_0.zip --runner=metacomm --toolsets=msvc,vc7,vc-7_1,cw-8_3 --pjl-toolset=vc-7_1
5) That's it.
If you are using "collect_and_upload_logs.py", simply change '--tag=RC_1_32_0" to "--tag=boost_1_32_0".
All test results will be uploaded to ftp://fx.meta-comm.com/boost-regression/boost_1_32_0/, picked up by the reporting tools, and displayed in the usual location -- http://www.meta-comm.com/engineering/boost-regression/developer/index.html.
Thank you!
-- 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"
Hello, On my computer the actual tar fails to compile the date_time and program_options with: - vc7.1 - stlport 4.6.2 i use the following cmdline to build boost: bjam "-sTOOLS=vc-7_1-stlport" "-sSTLPORT_PATH=E:\STLPort" "-sSTLPORT_VERSION=4.6.2" i got the following error-messages (multi-messages for the same error): date_time: vc-C++ bin\boost\libs\date_time\build\boost_date_time.dll\vc-7_1-stlport\debug\threading-multi\greg_month.obj greg_month.cpp F:\boost\boost_1_32_0\boost\lexical_cast.hpp(150) : error C2679: Bin„rer Operator '>>': Es konnte kein Operator gefunden werden, der einen rechtsseitigen Operator vom Typ 'boost::date_time::date_names_put<Config,charT,OutputIterator>::string_type' akzeptiert (oder keine geeignete Konvertierung m”glich) with [ Config=boost::gregorian::greg_facet_config, charT=wchar_t, OutputIterator=_STL::ostreambuf_iterator<wchar_t,_STL::char_traits<wchar_t>> ] Program-Options F:\boost\boost_1_32_0\boost\program_options\detail\utf8_codecvt_facet.hpp(70) : error C2039: 'codecvt': Ist kein Element von 'operator``global namespace''' regards, Sven
On Tue, 02 Nov 2004 16:52:35 +0100, Sven Johannsen wrote
Hello,
On my computer the actual tar fails to compile the date_time and program_options with: - vc7.1 - stlport 4.6.2
i use the following cmdline to build boost:
bjam "-sTOOLS=vc-7_1-stlport" "-sSTLPORT_PATH=E:\STLPort" "-sSTLPORT_VERSION=4.6.2"
i got the following error-messages (multi-messages for the same error): date_time: vc-C++ bin\boost\libs\date_time\build\boost_date_time.dll\vc-7_1- stlport\debug\threading-multi\greg_month.obj greg_month.cpp F:\boost\boost_1_32_0\boost\lexical_cast.hpp(150) : error C2679: [WINDOWS-1252?]Binrer Operator '>>': Es konnte kein Operator gefunden werden, der einen rechtsseitigen Operator vom Typ 'boost::date_time::date_names_put<Config,charT, OutputIterator>::string_type' akzeptiert (oder keine geeignete [WINDOWS-1252?]Konvertierung mglich) with [ Config=boost::gregorian::greg_facet_config, charT=wchar_t,
OutputIterator=_STL::ostreambuf_iterator<wchar_t,_STL::char_traits<wchar_t>> ]
Well, unfortunately we don't have VC7.1 with STLPort here to try this and I don't recall any of the regression testers using this combo either. My guess is that this is a problem with support for wchar_t with STLPort -- but it's just a guess. You could try and flip off the BOOST_NO_STD_LOCALE flag and see what happens -- this will avoid compiling any wchar_t stuff in date-time. Jeff
participants (4)
-
Aleksey Gurtovoy -
Jeff Garland -
Sven Johannsen -
Victor A. Wagner Jr.