[1.34.0] Release Candidate 3
Hi, 1.34.0 release candidate 3 is now available from: http://www.boost.org/release/. It contains a number of doc changes. Toolset version auto detection with msvc. And a fix for missing files in the install (bjam install). Please give it a try and report any problems to the developer list or directly to me. Unless it's broken in a major way it'll be released unchanged on Saturday May 12. Thanks Thomas -- Thomas Witt witt@acm.org
On 5/11/07, Thomas Witt <witt@acm.org> wrote:
Hi,
1.34.0 release candidate 3 is now available from:
Looks good to me. Built and tested on linux with both gcc version 3.4.6 20060404 (Red Hat 3.4.6-3) gcc version 4.1.0 20060515 (Red Hat 4.1.0-18) Good job Thomas! Regards, -- Tarjei
Hi, On 5/11/07, Thomas Witt <witt@acm.org> wrote:
1.34.0 release candidate 3 is now available from:
http://www.boost.org/release/.
It contains a number of doc changes. Toolset version auto detection with msvc. And a fix for missing files in the install (bjam install).
I confirm the toolset auto detection on MSVC works fine. Thanks for the real fast fix. with best regards, dhruva -- Dhruva Krishnamurthy Contents reflect my personal views only!
dhruva wrote:
Hi,
On 5/11/07, Thomas Witt <witt@acm.org> wrote:
1.34.0 release candidate 3 is now available from:
http://www.boost.org/release/.
It contains a number of doc changes. Toolset version auto detection with msvc. And a fix for missing files in the install (bjam install).
I confirm the toolset auto detection on MSVC works fine. Thanks for the real fast fix.
This one should go to Rene and Dave. I am just assembling bits and pieces. Thanks for checking! Thomas -- Thomas Witt witt@acm.org
Thomas Witt wrote:
Hi,
1.34.0 release candidate 3 is now available from:
http://www.boost.org/release/.
It contains a number of doc changes. Toolset version auto detection with msvc. And a fix for missing files in the install (bjam install).
Please give it a try and report any problems to the developer list or directly to me. When I build this (using bjam --toolset=msvc install) it installs to c:\boost\include\boost-1_35 and the library files have 1_35 as the version number. This was done with Borland/CodeGear Turbo C++ and with Microsoft VC 8.
Also, I tried to build with msvc-8.0 as the toolset and it told me that 8.0 was not a valid version number. I can use msvc as the toolset but then there is not a compiler version number in the resulting libraries. (i.e. libboost_thread-vc-mt-1_35.lib). Am I doing something wrong? Am I the only one seeing this issue? Jason
on Fri May 11 2007, Jason Stewart <jstewart-AT-pobox.com> wrote:
Thomas Witt wrote:
Hi,
1.34.0 release candidate 3 is now available from:
http://www.boost.org/release/.
It contains a number of doc changes. Toolset version auto detection with msvc. And a fix for missing files in the install (bjam install).
Please give it a try and report any problems to the developer list or directly to me. When I build this (using bjam --toolset=msvc install) it installs to c:\boost\include\boost-1_35 and the library files have 1_35 as the version number. This was done with Borland/CodeGear Turbo C++ and with Microsoft VC 8.
Also, I tried to build with msvc-8.0 as the toolset and it told me that 8.0 was not a valid version number. I can use msvc as the toolset but then there is not a compiler version number in the resulting libraries. (i.e. libboost_thread-vc-mt-1_35.lib).
Am I doing something wrong? Am I the only one seeing this issue?
The only way I can imagine this happening is if somehow the HEAD version of the Jamfile.v2 at BOOST_ROOT was substituted for the correct (RC_1_34_0) one. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com
on Sat May 12 2007, David Abrahams <dave-AT-boost-consulting.com> wrote:
on Fri May 11 2007, Jason Stewart <jstewart-AT-pobox.com> wrote:
Thomas Witt wrote:
Hi,
1.34.0 release candidate 3 is now available from:
http://www.boost.org/release/.
It contains a number of doc changes. Toolset version auto detection with msvc. And a fix for missing files in the install (bjam install).
Please give it a try and report any problems to the developer list or directly to me. When I build this (using bjam --toolset=msvc install) it installs to c:\boost\include\boost-1_35 and the library files have 1_35 as the version number. This was done with Borland/CodeGear Turbo C++ and with Microsoft VC 8.
Also, I tried to build with msvc-8.0 as the toolset and it told me that 8.0 was not a valid version number. I can use msvc as the toolset but then there is not a compiler version number in the resulting libraries. (i.e. libboost_thread-vc-mt-1_35.lib).
Am I doing something wrong? Am I the only one seeing this issue?
The only way I can imagine this happening is if somehow the HEAD version of the Jamfile.v2 at BOOST_ROOT was substituted for the correct (RC_1_34_0) one.
Nope. 1.35 and 1_35 don't appear anywhere in the tree that looks dangerous: find . \( -path \*/CVS -o -path \*/.svn -o -path \*/\{arch\} -o -path \*/.hg -o -path \*/_darcs -o -path \*/.git -o -path \*/.bzr \) -prune -o -type f -print0 | xargs -0 -e grep -Ei -nH -e 1\[._\]35\\\> ./boost/functional/hash/hash.hpp:46: // isn't due to be supported until Boost 1.35. So add support here. ./boost/preprocessor/repetition/repeat.hpp:86:# define BOOST_PP_REPEAT_1_35(m, d) BOOST_PP_REPEAT_1_34(m, d) m(2, 34, d) ./boost/preprocessor/repetition/repeat.hpp:87:# define BOOST_PP_REPEAT_1_36(m, d) BOOST_PP_REPEAT_1_35(m, d) m(2, 35, d) ./boost/test/unit_test_suite.hpp:212:// Revision 1.35 2006/02/06 10:04:55 rogeeff ./doc/html/thread/release_notes.html:87: been omitted from that release. A reworked mutex is expected to appear in 1.35. Binary file ./libs/graph/doc/isomorphism-impl.pdf matches Binary file ./libs/mpl/doc/refmanual.pdf matches ./libs/random/random-performance.html:261: <td>1.35</td> ./libs/regex/doc/vc71-performance.html:527: <td>1.35<BR> ./libs/test/test/errors_handling_test.cpp:210:// Revision 1.35 2005/06/13 11:46:26 schoepflin ./libs/thread/doc/release_notes.xml:57: been omitted from that release. A reworked mutex is expected to appear in 1.35. ./tools/build/v2/doc/userman.pdf:870:/Rect [ 277.23 524.56 451.35 514.56 ] I'm baffled. I have to try this out for myself. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com
on Fri May 11 2007, Jason Stewart <jstewart-AT-pobox.com> wrote:
Thomas Witt wrote:
Hi,
1.34.0 release candidate 3 is now available from:
http://www.boost.org/release/.
It contains a number of doc changes. Toolset version auto detection with msvc. And a fix for missing files in the install (bjam install).
Please give it a try and report any problems to the developer list or directly to me. When I build this (using bjam --toolset=msvc install) it installs to c:\boost\include\boost-1_35 and the library files have 1_35 as the version number. This was done with Borland/CodeGear Turbo C++ and with Microsoft VC 8.
Also, I tried to build with msvc-8.0 as the toolset and it told me that 8.0 was not a valid version number. I can use msvc as the toolset but then there is not a compiler version number in the resulting libraries. (i.e. libboost_thread-vc-mt-1_35.lib).
Am I doing something wrong? Am I the only one seeing this issue?
I can't reproduce it. Are you positive that you're not using Boost from the CVS HEAD? Please be absolutely certain that you're working with 1.34 RC3. The Jamfile.v2 at the root directory should contain this line: constant BOOST_VERSION : 1.34.0 ; If it doesn't, you're working with the wrong sources. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com
on Sat May 12 2007, David Abrahams <dave-AT-boost-consulting.com> wrote:
on Fri May 11 2007, Jason Stewart <jstewart-AT-pobox.com> wrote:
Thomas Witt wrote:
Hi,
1.34.0 release candidate 3 is now available from:
http://www.boost.org/release/.
It contains a number of doc changes. Toolset version auto detection with msvc. And a fix for missing files in the install (bjam install).
Please give it a try and report any problems to the developer list or directly to me. When I build this (using bjam --toolset=msvc install) it installs to c:\boost\include\boost-1_35 and the library files have 1_35 as the version number. This was done with Borland/CodeGear Turbo C++ and with Microsoft VC 8.
Also, I tried to build with msvc-8.0 as the toolset and it told me that 8.0 was not a valid version number. I can use msvc as the toolset but then there is not a compiler version number in the resulting libraries. (i.e. libboost_thread-vc-mt-1_35.lib).
Am I doing something wrong? Am I the only one seeing this issue?
I can't reproduce it. Are you positive that you're not using Boost from the CVS HEAD? Please be absolutely certain that you're working with 1.34 RC3. The Jamfile.v2 at the root directory should contain this line:
constant BOOST_VERSION : 1.34.0 ;
If it doesn't, you're working with the wrong sources.
Are you certain you don't have BOOST_ROOT or some other thing that might affect Boost.Build set in your environment? -- Dave Abrahams Boost Consulting http://www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com
David Abrahams wrote:
The following message is a courtesy copy of an article that has been posted to gmane.comp.lib.boost.devel as well.
on Fri May 11 2007, Jason Stewart <jstewart-AT-pobox.com> wrote:
Thomas Witt wrote:
Hi,
1.34.0 release candidate 3 is now available from:
http://www.boost.org/release/.
It contains a number of doc changes. Toolset version auto detection with msvc. And a fix for missing files in the install (bjam install).
Please give it a try and report any problems to the developer list or directly to me.
When I build this (using bjam --toolset=msvc install) it installs to c:\boost\include\boost-1_35 and the library files have 1_35 as the version number. This was done with Borland/CodeGear Turbo C++ and with Microsoft VC 8.
Also, I tried to build with msvc-8.0 as the toolset and it told me that 8.0 was not a valid version number. I can use msvc as the toolset but then there is not a compiler version number in the resulting libraries. (i.e. libboost_thread-vc-mt-1_35.lib).
Am I doing something wrong? Am I the only one seeing this issue?
I can't reproduce it. Are you positive that you're not using Boost from the CVS HEAD? Please be absolutely certain that you're working with 1.34 RC3. The Jamfile.v2 at the root directory should contain this line:
constant BOOST_VERSION : 1.34.0 ;
If it doesn't, you're working with the wrong sources.
Yes, sorry for the false alarm. I unzipped it and then changed to the wrong directory. Thanks for the pointer. Jason
Hallo, Thomas. Thomas Witt wrote: [...]
Please give it a try and report any problems to the developer list or directly to me.
There's a problem with the Serialization documentation, see http://article.gmane.org/gmane.comp.lib.boost.devel/159061. I guess you missed my message and I forgot to insist. The attached patch fixes it; I'm more than willing to apply it myself, but that won't happen before mid-morning tomorrow, Middle Europe Time. Let me know if you think it can go in. Cheers, Nicola Musatti Index: release.html =================================================================== RCS file: /cvsroot/boost/boost/libs/serialization/doc/release.html,v retrieving revision 1.12.2.3 diff -d -u -r1.12.2.3 release.html --- release.html 16 Jul 2006 01:55:37 -0000 1.12.2.3 +++ release.html 11 May 2007 22:24:17 -0000 @@ -41,11 +41,17 @@ older compilers - specificallly MSVC 6, Borland and GCC < 3.0. If you are using one of these compilers, you may download a version of spirit 1.6 <a href="http://spirit.sourceforge.net/index.php?doc=download/index.html">here</a>.. +Choose the latest 1.6.x Spirit only version available. To use this downloaded version rather than the one included with boost, -set an environmental variable SPIRIT_ROOT to be equal to the root -directory where the downloaded copy of spirit has been placed. E. G. +you have two options: either replace the <code style="white-space: normal">boost/spirit</code> and +<code style="white-space: normal">libs/spirit</code> directories, as well as the +<code style="white-space: normal">boost/spirit.hpp</code> header, with those in the downloaded version, +or extract Spirit 1.6 to a different directory and add the corresponding include directive to your +<code style="white-space: normal">tools/build/v2/user-config.jam</code> file for all the +compilers that need it, as in the following example: <pre><code> -set SPIRIT_ROOT=c:/spirit16 +using borland : 5.6.4 : "C:/Program Files/Borland/CBuilder6/Bin/bcc32" : + <cxxflags>-IC:/spirit1.6 ; </code></pre> If you're not using bjam and the Jamfile to build the library, be sure that the directory which contains the version of spirit you plan to use is placed
participants (6)
-
David Abrahams -
dhruva -
Jason Stewart -
Nicola Musatti -
Tarjei Knapstad -
Thomas Witt