[1.49.0] Beta 1 release candidates available
Release candidate files for 1.49.0 beta 1 are available at http://boost.cowic.de/rc/ As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. This helps ensure the candidates build OK before we push them out to SourceForge. Thanks, --The release managers --PS: I downloaded the 7z version, and it build without errors on Win7/VC++ Express 2010 sp1
On Jan 23, 2012, at 11:04 AM, Beman Dawes wrote:
Release candidate files for 1.49.0 beta 1 are available at http://boost.cowic.de/rc/
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Compiled without problems on Mac OS X 10.7.2 (gcc 4.2.1) Running the regression tests: ...failed updating 32 targets... ...skipped 54 targets... ...updated 32380 targets... ...failed testing.capture-output ../bin.v2/libs/asio/test/ip_multicast.test/darwin-4.2.1/debug/threading-multi/ip_multicast.run… ...failed testing.capture-output ../bin.v2/libs/asio/test/ip_multicast_select.test/darwin-4.2.1/debug/threading-multi/ip_multicast_select.run... ...failed darwin.compile.c++ ../bin.v2/libs/concept_check/stl_concept_covering.test/darwin-4.2.1/debug/stl_concept_covering.o... ...failed darwin.compile.c++ ../bin.v2/libs/detail/test/container_fwd/correctly_disable.test/darwin-4.2.1/debug/correctly_disable.o… ...failed darwin.compile.c++ ../bin.v2/libs/function_types/test/nonmember_ccs.test/darwin-4.2.1/debug/nonmember_ccs.o... ...failed darwin.compile.c++ ../bin.v2/libs/function_types/test/nonmember_ccs_exact.test/darwin-4.2.1/debug/nonmember_ccs_exact.o... ...failed darwin.compile.c++ ../bin.v2/libs/function_types/test/member_ccs.test/darwin-4.2.1/debug/member_ccs.o... ...failed darwin.compile.c++ ../bin.v2/libs/function_types/test/member_ccs_exact.test/darwin-4.2.1/debug/member_ccs_exact.o... ...failed darwin.compile.c++ ../bin.v2/libs/numeric/ublas/test/concepts.test/darwin-4.2.1/debug/concepts.o... ...failed testing.capture-output ../bin.v2/libs/optional/test/optional_test_ref.test/darwin-4.2.1/debug/optional_test_ref.run... ...failed darwin.compile.c++ ../bin.v2/libs/pool/test/test_bug_1252.test/darwin-4.2.1/debug/test_bug_1252.o... ...failed testing.capture-output ../bin.v2/libs/ptr_container/test/serialization.test/darwin-4.2.1/debug/serialization.run... ...failed darwin.link ../bin.v2/libs/spirit/repository/test/qi_repo_distinct.test/darwin-4.2.1/debug/qi_repo_distinct... ...failed darwin.link ../bin.v2/libs/spirit/repository/test/qi_repo_advance.test/darwin-4.2.1/debug/qi_repo_advance... ...failed darwin.link ../bin.v2/libs/spirit/repository/test/qi_repo_confix.test/darwin-4.2.1/debug/qi_repo_confix... ...failed darwin.link ../bin.v2/libs/spirit/repository/test/qi_repo_seek.test/darwin-4.2.1/debug/qi_repo_seek... ...failed darwin.link ../bin.v2/libs/spirit/repository/test/karma_repo_confix.test/darwin-4.2.1/debug/karma_repo_confix... ...failed darwin.link ../bin.v2/libs/spirit/repository/test/qi_repo_keywords.test/darwin-4.2.1/debug/qi_repo_keywords... ...failed darwin.compile.c++ ../bin.v2/libs/spirit/repository/test/karma_repo_subrule.test/darwin-4.2.1/debug/karma/subrule.o... ...failed darwin.link ../bin.v2/libs/spirit/repository/test/qi_repo_subrule.test/darwin-4.2.1/debug/qi_repo_subrule... ...failed darwin.compile.c++ ../bin.v2/libs/thread/test/test_thread_return_local.test/darwin-4.2.1/debug/threading-multi/test_thread_return_local.o... ...failed darwin.compile.c++ ../bin.v2/libs/thread/test/test_thread_return_local_lib.test/darwin-4.2.1/debug/threading-multi/test_thread_return_local.o... ...failed darwin.compile.c++ ../bin.v2/libs/thread/test/test_thread_move_return.test/darwin-4.2.1/debug/threading-multi/test_thread_move_return.o... ...failed darwin.compile.c++ ../bin.v2/libs/thread/test/test_thread_move_return_lib.test/darwin-4.2.1/debug/threading-multi/test_thread_move_return.o... ...failed darwin.compile.c++ ../bin.v2/libs/tr1/test/test_cmath_tricky.test/darwin-4.2.1/debug/test_cmath_tricky.o... ...failed darwin.compile.c++ ../bin.v2/libs/tr1/test/std_test_cmath_tricky.test/darwin-4.2.1/debug/std_test_cmath_tricky.o... ...failed darwin.compile.c++ ../bin.v2/libs/tr1/test/test_mem_fn_tricky.test/darwin-4.2.1/debug/test_mem_fn_tricky.o... ...failed darwin.compile.c++ ../bin.v2/libs/tr1/test/std_test_mem_fn_tricky.test/darwin-4.2.1/debug/std_test_mem_fn_tricky.o... ...failed darwin.compile.c++ ../bin.v2/libs/tr1/test/test_ref_wrapper_tricky.test/darwin-4.2.1/debug/test_ref_wrapper_tricky.o... ...failed darwin.compile.c++ ../bin.v2/libs/tr1/test/std_test_ref_wrapper_tricky.test/darwin-4.2.1/debug/std_test_ref_wrapper_tricky.o... ...failed testing.capture-output ../bin.v2/libs/tr1/test/run_random.test/darwin-4.2.1/debug/run_random.run... ...failed testing.capture-output ../bin.v2/libs/tr1/test/std_run_random.test/darwin-4.2.1/debug/std_run_random.run... (starting clang run now...) -- Marshall
On Jan 23, 2012, at 3:28 PM, Marshall Clow wrote:
On Jan 23, 2012, at 11:04 AM, Beman Dawes wrote:
Release candidate files for 1.49.0 beta 1 are available at http://boost.cowic.de/rc/
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
(starting clang run now…)
Apple Clang 3.0 (part of Xcode 4.2.1), Mac OS X 10.7.2, x86_64 $ ../b2 [ 208,784 lines of output skipped ] ...failed updating 36 targets... ...skipped 68 targets... ...updated 32410 targets... ...failed clang-darwin.compile.c++ ../bin.v2/libs/variant/test/variant_reference_test.test/clang-darwin-4.2.1/debug/variant_reference_test.o... ...failed testing.capture-output ../bin.v2/libs/asio/test/ip_multicast.test/clang-darwin-4.2.1/debug/threading-multi/ip_multicast.run... ...failed testing.capture-output ../bin.v2/libs/asio/test/ip_multicast_select.test/clang-darwin-4.2.1/debug/threading-multi/ip_multicast_select.run... ...failed clang-darwin.compile.c++ ../bin.v2/libs/concept_check/stl_concept_covering.test/clang-darwin-4.2.1/debug/stl_concept_covering.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/detail/test/container_fwd/correctly_disable.test/clang-darwin-4.2.1/debug/correctly_disable.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/function_types/test/nonmember_ccs.test/clang-darwin-4.2.1/debug/nonmember_ccs.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/function_types/test/nonmember_ccs_exact.test/clang-darwin-4.2.1/debug/nonmember_ccs_exact.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/function_types/test/member_ccs.test/clang-darwin-4.2.1/debug/member_ccs.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/function_types/test/member_ccs_exact.test/clang-darwin-4.2.1/debug/member_ccs_exact.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/fusion/test/invoke.test/clang-darwin-4.2.1/debug/functional/invoke.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/numeric/ublas/test/test1.test/clang-darwin-4.2.1/debug/test11.o... ...failed testing.capture-output ../bin.v2/libs/phoenix/test/switch_tests.test/clang-darwin-4.2.1/debug/switch_tests.run... ...failed clang-darwin.compile.c++ ../bin.v2/libs/polygon/test/gtl_boost_unit_test.test/clang-darwin-4.2.1/debug/gtl_boost_unit_test.o... ...failed testing.capture-output ../bin.v2/libs/ptr_container/test/serialization.test/clang-darwin-4.2.1/debug/serialization.run... ...failed clang-darwin.compile.c++ ../bin.v2/libs/spirit/test/karma_repeat1-p3.test/clang-darwin-4.2.1/debug/phoenix_v3-on/karma/repeat1.o... ...failed clang-darwin.link ../bin.v2/libs/spirit/repository/test/qi_repo_advance.test/clang-darwin-4.2.1/debug/qi_repo_advance... ...failed clang-darwin.link ../bin.v2/libs/spirit/repository/test/qi_repo_confix.test/clang-darwin-4.2.1/debug/qi_repo_confix... ...failed clang-darwin.link ../bin.v2/libs/spirit/repository/test/qi_repo_distinct.test/clang-darwin-4.2.1/debug/qi_repo_distinct... ...failed clang-darwin.link ../bin.v2/libs/spirit/repository/test/qi_repo_seek.test/clang-darwin-4.2.1/debug/qi_repo_seek... ...failed clang-darwin.link ../bin.v2/libs/spirit/repository/test/qi_repo_keywords.test/clang-darwin-4.2.1/debug/qi_repo_keywords... ...failed clang-darwin.link ../bin.v2/libs/spirit/repository/test/qi_repo_subrule.test/clang-darwin-4.2.1/debug/qi_repo_subrule... ...failed clang-darwin.link ../bin.v2/libs/spirit/repository/test/karma_repo_confix.test/clang-darwin-4.2.1/debug/karma_repo_confix... ...failed clang-darwin.compile.c++ ../bin.v2/libs/spirit/repository/test/karma_repo_subrule.test/clang-darwin-4.2.1/debug/karma/subrule.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/thread/test/test_thread_return_local.test/clang-darwin-4.2.1/debug/threading-multi/test_thread_return_local.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/thread/test/test_thread_return_local_lib.test/clang-darwin-4.2.1/debug/threading-multi/test_thread_return_local.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/thread/test/test_thread_move_return.test/clang-darwin-4.2.1/debug/threading-multi/test_thread_move_return.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/thread/test/test_thread_move_return_lib.test/clang-darwin-4.2.1/debug/threading-multi/test_thread_move_return.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/tr1/test/test_cmath_tricky.test/clang-darwin-4.2.1/debug/test_cmath_tricky.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/tr1/test/std_test_cmath_tricky.test/clang-darwin-4.2.1/debug/std_test_cmath_tricky.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/tr1/test/test_mem_fn_tricky.test/clang-darwin-4.2.1/debug/test_mem_fn_tricky.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/tr1/test/std_test_mem_fn_tricky.test/clang-darwin-4.2.1/debug/std_test_mem_fn_tricky.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/tr1/test/test_ref_wrapper_tricky.test/clang-darwin-4.2.1/debug/test_ref_wrapper_tricky.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/tr1/test/std_test_ref_wrapper_tricky.test/clang-darwin-4.2.1/debug/std_test_ref_wrapper_tricky.o... ...failed testing.capture-output ../bin.v2/libs/tr1/test/run_random.test/clang-darwin-4.2.1/debug/run_random.run... ...failed testing.capture-output ../bin.v2/libs/tr1/test/std_run_random.test/clang-darwin-4.2.1/debug/std_run_random.run... ...failed clang-darwin.compile.c++ ../bin.v2/libs/units/test/test_cmath.test/clang-darwin-4.2.1/debug/test_cmath.o...
A lot of build errors, while building under Linux with gcc (some of them): gcc.compile.c++ bin.v2/libs/regex/build/gcc/release/threading-multi/c_regex_traits.o /bin/sh: -ftemplate-depth-128: not found -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pedantic -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_REGEX_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/regex/build/gcc/release/threading-multi/c_regex_traits.o" "libs/regex/build/../src/c_regex_traits.cpp" ...failed gcc.compile.c++ bin.v2/libs/regex/build/gcc/release/threading-multi/c_regex_traits.o... gcc.compile.c++ bin.v2/libs/regex/build/gcc/release/threading-multi/cpp_regex_traits.o /bin/sh: -ftemplate-depth-128: not found -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pedantic -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_REGEX_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/regex/build/gcc/release/threading-multi/cpp_regex_traits.o" "libs/regex/build/../src/cpp_regex_traits.cpp" Best regards, Antony Polukhin
On Tue, Jan 24, 2012 at 12:40 PM, Antony Polukhin <antoshkka@gmail.com>wrote:
A lot of build errors, while building under Linux with gcc (some of them):
gcc.compile.c++ bin.v2/libs/regex/build/gcc/release/threading-multi/c_regex_traits.o /bin/sh: -ftemplate-depth-128: not found
-ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pedantic -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_REGEX_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/regex/build/gcc/release/threading-multi/c_regex_traits.o" "libs/regex/build/../src/c_regex_traits.cpp"
...failed gcc.compile.c++ bin.v2/libs/regex/build/gcc/release/threading-multi/c_regex_traits.o... gcc.compile.c++ bin.v2/libs/regex/build/gcc/release/threading-multi/cpp_regex_traits.o /bin/sh: -ftemplate-depth-128: not found
-ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pedantic -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_REGEX_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/regex/build/gcc/release/threading-multi/cpp_regex_traits.o" "libs/regex/build/../src/cpp_regex_traits.cpp"
Hum... That doesn't sound good. John? Thanks for the report! --Beman
This looks like a configuration problem as the toolset command is missing from the commands. We need to know the toolset setup and the commands used to build. Rene. On Jan 24, 2012, at 1:37 PM, Beman Dawes <bdawes@acm.org> wrote:
On Tue, Jan 24, 2012 at 12:40 PM, Antony Polukhin <antoshkka@gmail.com>wrote:
A lot of build errors, while building under Linux with gcc (some of them):
gcc.compile.c++ bin.v2/libs/regex/build/gcc/release/threading-multi/c_regex_traits.o /bin/sh: -ftemplate-depth-128: not found
-ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pedantic -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_REGEX_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/regex/build/gcc/release/threading-multi/c_regex_traits.o" "libs/regex/build/../src/c_regex_traits.cpp"
...failed gcc.compile.c++ bin.v2/libs/regex/build/gcc/release/threading-multi/c_regex_traits.o... gcc.compile.c++ bin.v2/libs/regex/build/gcc/release/threading-multi/cpp_regex_traits.o /bin/sh: -ftemplate-depth-128: not found
-ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pedantic -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_REGEX_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/regex/build/gcc/release/threading-multi/cpp_regex_traits.o" "libs/regex/build/../src/cpp_regex_traits.cpp"
Hum... That doesn't sound good.
John?
Thanks for the report!
--Beman
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
...failed gcc.compile.c++ bin.v2/libs/regex/build/gcc/release/threading-multi/c_regex_traits.o... gcc.compile.c++ bin.v2/libs/regex/build/gcc/release/threading-multi/cpp_regex_traits.o /bin/sh: -ftemplate-depth-128: not found
-ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pedantic -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_REGEX_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/regex/build/gcc/release/threading-multi/cpp_regex_traits.o" "libs/regex/build/../src/cpp_regex_traits.cpp"
Hum... That doesn't sound good.
John?
Nothing much changed in Boost.Regex, looks like a Boost.Build or configuration setup issue to me, we need to see the user-config.jam probably. John.
On Tue, Jan 24, 2012 at 12:15 PM, Marshall Clow <mclow.lists@gmail.com>wrote:
On Jan 23, 2012, at 3:28 PM, Marshall Clow wrote:
On Jan 23, 2012, at 11:04 AM, Beman Dawes wrote:
Release candidate files for 1.49.0 beta 1 are available at http://boost.cowic.de/rc/
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
(starting clang run now…)
Apple Clang 3.0 (part of Xcode 4.2.1), Mac OS X 10.7.2, x86_64
$ ../b2 [ 208,784 lines of output skipped ] ...failed updating 36 targets... ...skipped 68 targets... ...updated 32410 targets...
...failed clang-darwin.compile.c++ ../bin.v2/libs/variant/test/variant_reference_test.test/clang-darwin-4.2.1/debug/variant_reference_test.o... ...failed testing.capture-output ../bin.v2/libs/asio/test/ip_multicast.test/clang-darwin-4.2.1/debug/threading-multi/ip_multicast.run... ...failed testing.capture-output ../bin.v2/libs/asio/test/ip_multicast_select.test/clang-darwin-4.2.1/debug/threading-multi/ip_multicast_select.run... ...failed clang-darwin.compile.c++ ../bin.v2/libs/concept_check/stl_concept_covering.test/clang-darwin-4.2.1/debug/stl_concept_covering.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/detail/test/container_fwd/correctly_disable.test/clang-darwin-4.2.1/debug/correctly_disable.o... ...failed clang-darwin.compile.c++ ../bin.v2/libs/function_types/test/nonmember_ccs.test/clang-darwin-4.2.1/debug/nonmember_ccs.o...
Sorry to be so ignorant of Clang status for Boost, but are those expected or unexpected errors? --Beman
----- Original Message -----
From: Beman Dawes <bdawes@acm.org> To: Boost Developers List <boost@lists.boost.org> Cc: Sent: Monday, January 23, 2012 9:04 PM Subject: [boost] [1.49.0] Beta 1 release candidates available
Release candidate files for 1.49.0 beta 1 are available at http://boost.cowic.de/rc/
Where are release notes and how can they be updated? Artyom Beilis -------------- CppCMS - C++ Web Framework: http://cppcms.sf.net/ CppDB - C++ SQL Connectivity: http://cppcms.sf.net/sql/cppdb/
On 24 January 2012 10:01, Artyom Beilis <artyomtnk@yahoo.com> wrote:
Where are release notes and how can they be updated?
The page is at: http://www.boost.org/users/history/version_1_49_0.html This time, I plan to add a link to the home page soon after the beta is released. To update the notes you can email me, or do it yourself at: https://svn.boost.org/svn/boost/website/public_html/live/feed/history/ To actually update the site you need python and quickbook (ideally built from the stable release) on your path. If you don't want to install quickbook, then don't worry too much about quickbook syntax, I'll sort out the syntax when I update the site. To do it yourself, you need to check out the whole site: https://svn.boost.org/svn/boost/website/public_html/live/ There are some instructions at: http://www.boost.org/development/website_updating.html#Feeds
From: Daniel James <dnljms@gmail.com>
On 24 January 2012 10:01, Artyom Beilis <artyomtnk@yahoo.com> wrote:
Where are release notes and how can they be updated?
The page is at:
http://www.boost.org/users/history/version_1_49_0.html
This time, I plan to add a link to the home page soon after the beta is released.
To update the notes you can email me, or do it yourself at:
Only small note: Boost.Locale "Fixed incorrect use of MultiByteToWideChar in detection of invalid input sequences"
https://svn.boost.org/svn/boost/website/public_html/live/feed/history/
To actually update the site you need python and quickbook (ideally built from the stable release) on your path. If you don't want to install quickbook, then don't worry too much about quickbook syntax, I'll sort out the syntax when I update the site. To do it yourself, you need to check out the whole site:
https://svn.boost.org/svn/boost/website/public_html/live/
There are some instructions at:
http://www.boost.org/development/website_updating.html#Feeds
Ohhhh... I'd prefer not to setup entire quickbook path :-) Thanks! Artyom>
On 24 January 2012 13:11, Artyom Beilis <artyomtnk@yahoo.com> wrote:
Boost.Locale
"Fixed incorrect use of MultiByteToWideChar in detection of invalid input sequences"
Updated.
Ohhhh... I'd prefer not to setup entire quickbook path :-)
You just need the executable (ie. do something like 'cd $BOOST_ROOT/tools/quickbook && b2 && cp ../../dist/bin/quickbook ~/bin'), the conversion from boostbook to html is done by a python script. This doesn't use xslt or the docbook toolchain.
On Tue, Jan 24, 2012, at 11:51 AM, Daniel James wrote:
On 24 January 2012 10:01, Artyom Beilis <artyomtnk@yahoo.com> wrote:
Where are release notes and how can they be updated?
The page is at:
http://www.boost.org/users/history/version_1_49_0.html
This time, I plan to add a link to the home page soon after the beta is released.
To update the notes you can email me, or do it yourself at:
Boost.Uuid - fixed https://svn.boost.org/trac/boost/ticket/6258 - fixed https://svn.boost.org/trac/boost/ticket/5325 (sha1 implementation handles messages as long as the specification) - progress on https://svn.boost.org/trac/boost/ticket/6118 (there are fewer warnings) < ... > Regards, Andy Tompkins
Hi Daniel, On 24-1-2012 12:51, Daniel James wrote:
On 24 January 2012 10:01, Artyom Beilis<artyomtnk@yahoo.com> wrote:
Where are release notes and how can they be updated? https://svn.boost.org/svn/boost/website/public_html/live/feed/history/
To actually update the site you need python and quickbook (ideally built from the stable release) on your path. If you don't want to install quickbook, then don't worry too much about quickbook syntax, I'll sort out the syntax when I update the site. To do it yourself, you need to check out the whole site:
Thanks for taking care. I have inserted the updates for Boost.Geometry. They come from ".....\libs\geometry\doc\release_notes.qbk" which we now have. I conformed w.r.t. syntax to the pieces above and below but did (could) not verify how it looks like after running Quickbook. Regards, Barend
2012/1/24 René Rivera <grafikrobot@gmail.com>:
This looks like a configuration problem as the toolset command is missing from the commands. We need to know the toolset setup and the commands used to build.
Commands used to build: ./b2 OS: Ubuntu 11.04 Compiler: gcc (i have got a lot of gccs, but the default is 4.6.1) It looks like there is a newline symbol in all gcc.compile.c++ lines (between object file name and -ftemplate-depth-128): gcc.compile.c++ bin.v2/libs/python/build/gcc/release/link-static/threading-multi/object/inheritance.o -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.7" -c -o "bin.v2/libs/python/build/gcc/release/link-static/threading-multi/object/inheritance.o" "libs/python/src/object/inheritance.cpp" /bin/sh: -ftemplate-depth-128: not found Best regards, Antony Polukhin
AMDG On 01/24/2012 08:02 PM, Antony Polukhin wrote:
2012/1/24 René Rivera <grafikrobot@gmail.com>:
This looks like a configuration problem as the toolset command is missing from the commands. We need to know the toolset setup and the commands used to build.
Commands used to build: ./b2 OS: Ubuntu 11.04 Compiler: gcc (i have got a lot of gccs, but the default is 4.6.1)
It looks like there is a newline symbol in all gcc.compile.c++ lines (between object file name and -ftemplate-depth-128):
The newline is expected. The problem is that "g++" is missing. Check the output of ./b2 --debug-configuration to figure out what's wrong.
gcc.compile.c++ bin.v2/libs/python/build/gcc/release/link-static/threading-multi/object/inheritance.o
-ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.7" -c -o "bin.v2/libs/python/build/gcc/release/link-static/threading-multi/object/inheritance.o" "libs/python/src/object/inheritance.cpp"
/bin/sh: -ftemplate-depth-128: not found
In Christ, Steven Watanabe
2012/1/25 Steven Watanabe <watanabesj@gmail.com>:
The newline is expected. The problem is that "g++" is missing. Check the output of ./b2 --debug-configuration to figure out what's wrong.
Compiler is clang-2.9 (totaly forgot about user-config.jam, thought that gcc.compile.c++ in output means gcc) user-config.jam has a single line `using clang ;' ./b2 --debug-configuration gave me the following : notice: found boost-build.jam at /home/antoshkka/Downloads/boost_1_49_0_beta1/boost-build.jam notice: loading Boost.Build from /home/antoshkka/Downloads/boost_1_49_0_beta1/tools/build/v2 notice: Searching /etc /home/antoshkka /home/antoshkka/Downloads/boost_1_49_0_beta1/tools/build/v2 /usr/share/boost-build /home/antoshkka/Down loads/boost_1_49_0_beta1/tools/build/v2/kernel /home/antoshkka/Downloads/boost_1_49_0_beta1/tools/build/v2/util /home/antoshkka/Downloads/boos t_1_49_0_beta1/tools/build/v2/build /home/antoshkka/Downloads/boost_1_49_0_beta1/tools/build/v2/tools /home/antoshkka/Downloads/boost_1_49_0_b eta1/tools/build/v2/contrib /home/antoshkka/Downloads/boost_1_49_0_beta1/tools/build/v2/. for site-config configuration file site-config.jam . notice: Loading site-config configuration file site-config.jam from /home/antoshkka/Downloads/boost_1_49_0_beta1/tools/build/v2/site-config.ja m . notice: Searching /home/antoshkka /home/antoshkka/Downloads/boost_1_49_0_beta1/tools/build/v2 /usr/share/boost-build /home/antoshkka/Downloads /boost_1_49_0_beta1/tools/build/v2/kernel /home/antoshkka/Downloads/boost_1_49_0_beta1/tools/build/v2/util /home/antoshkka/Downloads/boost_1_4 9_0_beta1/tools/build/v2/build /home/antoshkka/Downloads/boost_1_49_0_beta1/tools/build/v2/tools /home/antoshkka/Downloads/boost_1_49_0_beta1/ tools/build/v2/contrib /home/antoshkka/Downloads/boost_1_49_0_beta1/tools/build/v2/. for user-config configuration file user-config.jam . notice: Loading user-config configuration file user-config.jam from /home/antoshkka/user-config.jam . notice: will use 'clang++' for clang-linux, condition <toolset>clang-linux-2.9 notice: Searching for project-config configuration file project-config.jam . notice: Loading project-config configuration file project-config.jam from project-config.jam . <...> gcc.compile.c++ bin.v2/libs/regex/build/gcc/release/threading-multi/c_regex_traits.o /bin/sh: -ftemplate-depth-128: not found -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pedantic -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_REGEX_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/regex/build/gcc/release/threading-multi/c_regex_traits.o" "libs/regex/build/../src/c_regex_traits.cpp" ...failed gcc.compile.c++ bin.v2/libs/regex/build/gcc/release/threading-multi/c_regex_traits.o... <...> Is it ok for clang-2.9 to use gcc.compile.c++ ? Best regards, Antony Polukhin
On 1/25/2012 11:41 AM, Antony Polukhin wrote:
2012/1/25 Steven Watanabe<watanabesj@gmail.com>:
The newline is expected. The problem is that "g++" is missing. Check the output of ./b2 --debug-configuration to figure out what's wrong.
Compiler is clang-2.9 (totaly forgot about user-config.jam, thought that gcc.compile.c++ in output means gcc) user-config.jam has a single line `using clang ;'
[...]
Is it ok for clang-2.9 to use gcc.compile.c++ ?
No. Since clang is not the default on *nix you need to specify to compile with it on the command line: ./b2 toolset=clang -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
Hi Anthony, On Wednesday, 25. January 2012 18:41:02 Antony Polukhin wrote:
2012/1/25 Steven Watanabe <watanabesj@gmail.com>:
The newline is expected. The problem is that "g++" is missing. Check the output of ./b2 --debug-configuration to figure out what's wrong.
Compiler is clang-2.9 (totaly forgot about user-config.jam, thought that gcc.compile.c++ in output means gcc) user-config.jam has a single line `using clang ;'
./b2 --debug-configuration gave me the following :
notice: will use 'clang++' for clang-linux, condition <toolset>clang-linux-2.9 notice: Searching for project-config configuration file project-config.jam . notice: Loading project-config configuration file project-config.jam from project-config.jam .
Okay, clang is detected. But no gcc which is the default compiler.
gcc.compile.c++ bin.v2/libs/regex/build/gcc/release/threading-multi/c_regex_traits.o /bin/sh: -ftemplate-depth-128: not found
And so a command without "g++" is issued.
Is it ok for clang-2.9 to use gcc.compile.c++ ?
Yes, but you have to run "b2 clang" to select it. Seems the implicit autodefault of "g++" should be changed for system without any gcc installation. Yours, Jürgen -- Dipl.-Math. Jürgen Hunold | IVE mbH Software-Entwickler | Lützerodestraße 10 Tel: +49 511 897668 33 | 30161 Hannover, Germany Fax: +49 511 897668 29 | http://www.ivembh.de juergen.hunold@ivembh.de | | Geschäftsführer: Sitz des Unternehmens: Hannover | Univ.-Prof. Dr.-Ing. Thomas Siefer Amtsgericht Hannover, HRB 56965 | PD Dr.-Ing. Alfons Radtke
2012/1/26 Jürgen Hunold <juergen.hunold@ivembh.de>:
On Wednesday, 25. January 2012 18:41:02 Antony Polukhin wrote:
notice: will use 'clang++' for clang-linux, condition <toolset>clang-linux-2.9 notice: Searching for project-config configuration file project-config.jam . notice: Loading project-config configuration file project-config.jam from project-config.jam .
Okay, clang is detected. But no gcc which is the default compiler.
Removed user-config.jam. Successful build with gcc-4.6.1 (./b2) Successful build with clang-2.9 (./b2 toolset=clang) Best regards, Antony Polukhin
On 24.01.2012, at 12:51, Daniel James wrote:
To update the notes you can email me, or do it yourself at:
Hi, * [phrase library..[@/libs/conversion/lexical_cast.htm Lexical cast]:] * Fixed bugs and warnings: [@https://svn.boost.org/trac/boost/ticket/6127 #6127], [@https://svn.boost.org/trac/boost/ticket/6132 #6132], [@https://svn.boost.org/trac/boost/ticket/6159 #6159], [@https://svn.boost.org/trac/boost/ticket/6182 #6182], [@https://svn.boost.org/trac/boost/ticket/6186 #6186], [@https://svn.boost.org/trac/boost/ticket/6193 #6193], [@https://svn.boost.org/trac/boost/ticket/6264 #6264], [@https://svn.boost.org/trac/boost/ticket/6290 #6290], [@https://svn.boost.org/trac/boost/ticket/6298 #6298], [@https://svn.boost.org/trac/boost/ticket/6400 #6400]. Thanks for updating the file. Best regards, Antony Polukhin
Le 24/01/12 12:51, Daniel James a écrit :
On 24 January 2012 10:01, Artyom Beilis<artyomtnk@yahoo.com> wrote:
Where are release notes and how can they be updated? The page is at:
http://www.boost.org/users/history/version_1_49_0.html
This time, I plan to add a link to the home page soon after the beta is released.
To update the notes you can email me, or do it yourself at:
https://svn.boost.org/svn/boost/website/public_html/live/feed/history/
To actually update the site you need python and quickbook (ideally built from the stable release) on your path. If you don't want to install quickbook, then don't worry too much about quickbook syntax, I'll sort out the syntax when I update the site. To do it yourself, you need to check out the whole site:
https://svn.boost.org/svn/boost/website/public_html/live/
There are some instructions at:
http://www.boost.org/development/website_updating.html#Feeds
_______________________________________________ Unsubscribe& other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Hi, Please could you add the following changes for Boost.Thread * [phrase library..[@/libs/thread Thread]:] * Fixed Bugs: * [@http://svn.boost.org/trac/boost/ticket/2309 #2309] Lack of g++ symbol visibility support in Boost.Thread. * [@http://svn.boost.org/trac/boost/ticket/2639 #2639] documentation should be extended(defer_lock, try_to_lock, ...). * [@http://svn.boost.org/trac/boost/ticket/3639 #3639] Boost.Thread doesn't build with Sun-5.9 on Linux. * [@http://svn.boost.org/trac/boost/ticket/3762 #3762] Thread can't be compiled with winscw (Codewarrior by Nokia). * [@http://svn.boost.org/trac/boost/ticket/3885 #3885] document about mix usage of boost.thread and native thread api. * [@http://svn.boost.org/trac/boost/ticket/3975 #3975] Incorrect precondition for promise::set_wait_callback(). * [@http://svn.boost.org/trac/boost/ticket/4048 #4048] thread::id formatting involves locale * [@http://svn.boost.org/trac/boost/ticket/4315 #4315] gcc 4.4 Warning: inline ... declared as dllimport: attribute ignored. * [@http://svn.boost.org/trac/boost/ticket/4480 #4480] OpenVMS patches for compiler issues workarounds. * [@http://svn.boost.org/trac/boost/ticket/4819 #4819] boost.thread's documentation misprints. * [@http://svn.boost.org/trac/boost/ticket/5040 #5040] future.hpp in boost::thread does not compile with /clr. * [@http://svn.boost.org/trac/boost/ticket/5423 #5423] thread issues with C++0x. * [@http://svn.boost.org/trac/boost/ticket/5502 #5502] race condition between shared_mutex timed_lock and lock_shared. * [@http://svn.boost.org/trac/boost/ticket/5594 #5594] boost::shared_mutex not fully compatible with Windows CE. * [@http://svn.boost.org/trac/boost/ticket/5617 #5617] boost::thread::id copy ctor. * [@http://svn.boost.org/trac/boost/ticket/5739 #5739] set-but-not-used warnings with gcc-4.6. * [@http://svn.boost.org/trac/boost/ticket/5826 #5826] threads.cpp: resource leak on threads creation failure. * [@http://svn.boost.org/trac/boost/ticket/5839 #5839] thread.cpp: ThreadProxy leaks on exceptions. * [@http://svn.boost.org/trac/boost/ticket/5859 #5859] win32 shared_mutex constructor leaks on exceptions. * [@http://svn.boost.org/trac/boost/ticket/6100 #6100] Compute hardware_concurrency() using get_nprocs() on GLIBC systems. * [@http://svn.boost.org/trac/boost/ticket/6141 #6141] Compilation error when boost.thread and boost.move are used together. * [@http://svn.boost.org/trac/boost/ticket/6168 #6168] recursive_mutex is using wrong config symbol (possible typo). * [@http://svn.boost.org/trac/boost/ticket/6175 #6175] Compile error with SunStudio. * [@http://svn.boost.org/trac/boost/ticket/6200 #6200] patch to have condition_variable and mutex error better handle EINTR. * [@http://svn.boost.org/trac/boost/ticket/6207 #6207] shared_lock swap compiler error on clang 3.0 c++11. * [@http://svn.boost.org/trac/boost/ticket/6208 #6208] try_lock_wrapper swap compiler error on clang 3.0 c++11. Thanks, Vicente
Le 28/01/12 13:24, Vicente J. Botet Escriba a écrit :
Le 24/01/12 12:51, Daniel James a écrit :
On 24 January 2012 10:01, Artyom Beilis<artyomtnk@yahoo.com> wrote:
Where are release notes and how can they be updated? The page is at:
http://www.boost.org/users/history/version_1_49_0.html
This time, I plan to add a link to the home page soon after the beta is released.
To update the notes you can email me, or do it yourself at:
https://svn.boost.org/svn/boost/website/public_html/live/feed/history/
To actually update the site you need python and quickbook (ideally built from the stable release) on your path. If you don't want to install quickbook, then don't worry too much about quickbook syntax, I'll sort out the syntax when I update the site. To do it yourself, you need to check out the whole site:
https://svn.boost.org/svn/boost/website/public_html/live/
There are some instructions at:
http://www.boost.org/development/website_updating.html#Feeds
_______________________________________________ Unsubscribe& other changes:http://lists.boost.org/mailman/listinfo.cgi/boost
Hi,
Please could you add the following changes for Boost.Chrono * [phrase library..[@/libs/chrono Chrono]:] * Bug Fixes: * [@http://svn.boost.org/trac/boost/ticket/6092 #6092] Input from non integral durations makes the compiler fail. * [@http://svn.boost.org/trac/boost/ticket/6093 #6093] [1/3]second fails as valid duration input. * [@http://svn.boost.org/trac/boost/ticket/6113 #6113] duplicate symbol when BOOST_CHRONO_HEADER_ONLY is defined. * [@http://svn.boost.org/trac/boost/ticket/6243 #6243] Sandia-pgi-11.9: more than one instance of overloaded function "min" matches. * [@http://svn.boost.org/trac/boost/ticket/6257 #6257] process_cpu_clock::now() on linux gives time_points 1/1000 times. Thanks, Vicente
Hi,
The page is at:
http://www.boost.org/users/history/version_1_49_0.html Three links to ticket are wrong in Unordered.
https://svn.boost.org/trac/boost/tickets/6167 https://svn.boost.org/trac/boost/tickets/6311 https://svn.boost.org/trac/boost/tickets/6370 Should be followings. https://svn.boost.org/trac/boost/ticket/6167 https://svn.boost.org/trac/boost/ticket/6311 https://svn.boost.org/trac/boost/ticket/6370 Regards, Kohei
On 23/01/2012 19:04, Beman Dawes wrote:
Release candidate files for 1.49.0 beta 1 are available at http://boost.cowic.de/rc/
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
This helps ensure the candidates build OK before we push them out to SourceForge.
Compiled fine on VS10 x64 & x86. KTC
On Mon, Jan 23, 2012 at 2:04 PM, Beman Dawes <bdawes@acm.org> wrote:
Release candidate files for 1.49.0 beta 1 are available at http://boost.cowic.de/rc/
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Ubuntu 11.4 build failed. error: No best alternative for /python_for_extensions next alternative: required properties: <python>2.7 <target-os>linux matched next alternative: required properties: <python>2.7 <target-os>linux matched error: No best alternative for /python_for_extensions next alternative: required properties: <python>2.7 <target-os>linux matched next alternative: required properties: <python>2.7 <target-os>linux matched But it still tried to build Boost.Python, which failed every compile with a missing python header. There was on other failure: gcc.compile.c++ bin.v2/libs/signals/build/gcc-4.6/release/link-static/threading-multi/named_slot_map.o libs/signals/src/named_slot_map.cpp: In member function ‘void boost::signals::detail::named_slot_map::disconnect(const boost::signals::detail::stored_group&)’: libs/signals/src/named_slot_map.cpp:105:23: error: call of overloaded ‘erase(boost::signals::detail::named_slot_map::group_iterator&)’ is ambiguous libs/signals/src/named_slot_map.cpp:105:23: note: candidates are: /usr/include/c++/4.6/bits/stl_map.h:613:7: note: std::map<_Key, _Tp, _Compare, _Alloc>::iterator std::map<_Key, _Tp, _Compare, _Alloc>::erase(std::map<_Key, _Tp, _Compare, _Alloc>::const_iterator) [with _Key = boost::signals::detail::stored_group, _Tp = std::list<boost::signals::detail::connection_slot_pair>, _Compare = boost::function2<bool, boost::signals::detail::stored_group, boost::signals::detail::stored_group>, _Alloc = std::allocator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >, std::map<_Key, _Tp, _Compare, _Alloc>::iterator = std::_Rb_tree_iterator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >, std::map<_Key, _Tp, _Compare, _Alloc>::const_iterator = std::_Rb_tree_const_iterator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >] /usr/include/c++/4.6/bits/stl_map.h:643:7: note: std::map<_Key, _Tp, _Compare, _Alloc>::size_type std::map<_Key, _Tp, _Compare, _Alloc>::erase(const key_type&) [with _Key = boost::signals::detail::stored_group, _Tp = std::list<boost::signals::detail::connection_slot_pair>, _Compare = boost::function2<bool, boost::signals::detail::stored_group, boost::signals::detail::stored_group>, _Alloc = std::allocator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >, std::map<_Key, _Tp, _Compare, _Alloc>::size_type = unsigned int, std::map<_Key, _Tp, _Compare, _Alloc>::key_type = boost::signals::detail::stored_group] libs/signals/src/named_slot_map.cpp: In member function ‘void boost::signals::detail::named_slot_map::remove_disconnected_slots()’: libs/signals/src/named_slot_map.cpp:128:35: error: call of overloaded ‘erase(std::_Rb_tree_iterator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >::_Self)’ is ambiguous libs/signals/src/named_slot_map.cpp:128:35: note: candidates are: /usr/include/c++/4.6/bits/stl_map.h:613:7: note: std::map<_Key, _Tp, _Compare, _Alloc>::iterator std::map<_Key, _Tp, _Compare, _Alloc>::erase(std::map<_Key, _Tp, _Compare, _Alloc>::const_iterator) [with _Key = boost::signals::detail::stored_group, _Tp = std::list<boost::signals::detail::connection_slot_pair>, _Compare = boost::function2<bool, boost::signals::detail::stored_group, boost::signals::detail::stored_group>, _Alloc = std::allocator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >, std::map<_Key, _Tp, _Compare, _Alloc>::iterator = std::_Rb_tree_iterator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >, std::map<_Key, _Tp, _Compare, _Alloc>::const_iterator = std::_Rb_tree_const_iterator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >] /usr/include/c++/4.6/bits/stl_map.h:643:7: note: std::map<_Key, _Tp, _Compare, _Alloc>::size_type std::map<_Key, _Tp, _Compare, _Alloc>::erase(const key_type&) [with _Key = boost::signals::detail::stored_group, _Tp = std::list<boost::signals::detail::connection_slot_pair>, _Compare = boost::function2<bool, boost::signals::detail::stored_group, boost::signals::detail::stored_group>, _Alloc = std::allocator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >, std::map<_Key, _Tp, _Compare, _Alloc>::size_type = unsigned int, std::map<_Key, _Tp, _Compare, _Alloc>::key_type = boost::signals::detail::stored_group] These look like showstoppers to me; two libraries not building isn't good news! --Beman
Release candidate files for 1.49.0 beta 1 are available at
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
I downloaded the tar.bz2 version. I'm on an Apple computer running Mac OSX 10.7 (Lion) with a stock Xcode 3 (GCC 4.2.1) installation. The bootstrap script detected the "darwin" toolset but failed to load the Boost.Build engine. In the resulting log file, the first ten or so errors read "No such file or directory" wrt C header files. Let me know what else you need, or please advise. Cromwell D. Enage
I downloaded the tar.bz2 version.
I'm on an Apple computer running Mac OSX 10.7 (Lion) with a stock Xcode 3 (GCC 4.2.1) installation. The bootstrap script detected the "darwin" toolset but failed to load the Boost.Build engine. In the resulting log file, the first ten or so errors read "No such file or directory" wrt C header files.
Reinstalling Xcode fixed everything. Sorry for the noise. Cromwell D. Enage
On Mon, Jan 23, 2012 at 2:04 PM, Beman Dawes <bdawes@acm.org> wrote:
Release candidate files for 1.49.0 beta 1 are available at http://boost.cowic.de/rc/
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
On one hand, there have been an abnormally large number of build failure reports. On the other hand, most (if not all) seem to be user configuration issues rather than anything wrong with the beta itself. So on balance it seems OK to release the beta. I'll wait another 4 hours (IE until 12 noon eastern US time) to see if anyone disagrees, and then do the beta release. --Beman
Date: Mon, 23 Jan 2012 14:04:10 -0500 From: bdawes@acm.org
Release candidate files for 1.49.0 beta 1 are available at http://boost.cowic.de/rc/
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
This helps ensure the candidates build OK before we push them out to SourceForge.
I checked the 7z version and noticed that my (somewhat) re-do of Boost.CRC, including documentation, isn't there. Did I miss some cutoff date? I put the changes on the trunk; was I supposed to use a special branch? Daryle W.
On Friday, January 27, 2012 11:00:01 Daryle Walker wrote:
I checked the 7z version and noticed that my (somewhat) re-do of Boost.CRC, including documentation, isn't there. Did I miss some cutoff date? I put the changes on the trunk; was I supposed to use a special branch?
The "release" branch is used for official releases. Library maintainers are supposed to merge changes from trunk into branches/release as they pass testing.
From: andrey.semashev@gmail.com Date: Fri, 27 Jan 2012 20:05:27 +0400
On Friday, January 27, 2012 11:00:01 Daryle Walker wrote:
I checked the 7z version and noticed that my (somewhat) re-do of Boost.CRC, including documentation, isn't there. Did I miss some cutoff date? I put the changes on the trunk; was I supposed to use a special branch?
The "release" branch is used for official releases. Library maintainers are supposed to merge changes from trunk into branches/release as they pass testing.
Browsing my working copy with TortoiseSVN... The changes are BOOST-TRUNK/boost/crc.hpp at version 76335 and BOOST-TRUNK/libs/crc at version 76633. (The latter is a directory.) Furthermore, Boost.CRC is now using QuickBook documentation, so any Boost documentation scripts have to be changed. Has anyone tested the changes besides me?... (I use Apple-specific GCC 4.0.2 from Mac OS 10.4.11 [Tiger] on a PowerPC/G4 system.) Looking at the automated tests (after finding them) on the trunk, some compilers error out on my use of BOOST_AUTO and MSVC really hates the changes. Versions of MSVC before v11 give fatal errors. MSVC v11 lasts long enough to give an actual error; maybe fixing that will fix it for the other versions. Daryle W.
participants (19)
-
Andrey Semashev -
Andy Tompkins -
Antony Polukhin -
Artyom Beilis -
Barend Gehrels -
Beman Dawes -
Cromwell Enage -
Daniel James -
Daryle Walker -
John Maddock -
Jürgen Hunold -
Kohei Takahashi -
KTC -
Marshall Clow -
Rene Rivera -
René Rivera
-
Sebastian Redl -
Steven Watanabe -
Vicente J. Botet Escriba