[1.35.0] Release Candidate 2 available
1.35.0 Release Candidate 2 (RC2) is available at http://boost.cowic.de/rc/ RC2 fixes all of the serious issues reported for RC1. Note that links to the web site from the RC appear to be broken because the restructured web site will not go live until the actual release ships. In the meantime, the new website content is available at beta.boost.org. Please take the time to download RC2, and try to install it on your system. Kick the tires, and report any problems or issues you discover. Report by posting to either boost@lists.boost.org or boost-users@lists.boost.org. For a list of known issues, see http://svn.boost.org/trac/boost/wiki/MergeOneDotThreeFiveDotZero. Thanks, --Beman
Beman Dawes wrote:
1.35.0 Release Candidate 2 (RC2) is available at http://boost.cowic.de/rc/ RC2 fixes all of the serious issues reported for RC1.
Note that links to the web site from the RC appear to be broken because the restructured web site will not go live until the actual release ships. In the meantime, the new website content is available at beta.boost.org.
Please take the time to download RC2, and try to install it on your system. Kick the tires, and report any problems or issues you discover. Report by posting to either boost@lists.boost.org or boost-users@lists.boost.org.
For a list of known issues, see http://svn.boost.org/trac/boost/wiki/MergeOneDotThreeFiveDotZero.
There have only been a few issues raised, and we are almost done clearing them. That made me realize I should have asked not just for trouble reports, but success reports too. So if you downloaded RC2, please post a reply indicating what you've done with it, even if no problems or issues were detected. That way I can better gauge release readiness. Thanks, --Beman
On 23/03/2008, Beman Dawes <bdawes@acm.org> wrote:
Beman Dawes wrote:
1.35.0 Release Candidate 2 (RC2) is available at http://boost.cowic.de/rc/ RC2 fixes all of the serious issues reported for RC1.
Note that links to the web site from the RC appear to be broken because the restructured web site will not go live until the actual release ships. In the meantime, the new website content is available at beta.boost.org.
Please take the time to download RC2, and try to install it on your system. Kick the tires, and report any problems or issues you discover. Report by posting to either boost@lists.boost.org or boost-users@lists.boost.org.
For a list of known issues, see http://svn.boost.org/trac/boost/wiki/MergeOneDotThreeFiveDotZero.
There have only been a few issues raised, and we are almost done clearing them. That made me realize I should have asked not just for trouble reports, but success reports too.
So if you downloaded RC2, please post a reply indicating what you've done with it, even if no problems or issues were detected. That way I can better gauge release readiness.
Build was successful on my Fedora 8 laptop. Unit tests also ran successfully after I cleared up some disk space :) Docs look fine upon manual inspection, and make install seems to work fine (I haven't checked if there are missing headers or anything like that). Some minor comments: * A complete build with unit tests took several hours on a Intel Core2 T7200 with 2GB ram and helped itself to a whopping 4.6GB of disk. Maybe a note could be added to the 'check' target in the Makefile stating that it will take a long time and requires approx 4.6 gigs of disk? (I started 'make check' before leaving my apartment just to come back later finding it had stopped halfway through because I'd ran out of diskspace) * Docs are not installed. I would expect the docs to appear under $PREFIX/share/doc/boost-x.y/ * The headers are installed to $INCLUDEDIR/boost-1_35/boost, but I expected $INCLUDEDIR/boost. Supposing this is meant to enable parallel installs of different versions of boost I think this should be done using the --prefix option to configure, not hardcoded in the Jamfiles. (the static libraries and symlinks for the libs will be overwritten anyway if you attempt to install two versions to the same prefix). Other than that hings are looking good IMO, thanks for all your efforts to bring us a new release Beman! Regards, -- Tarjei Knapstad
Tarjei Knapstad wrote:
Build was successful on my Fedora 8 laptop. Unit tests also ran successfully after I cleared up some disk space :) Docs look fine upon manual inspection, and make install seems to work fine (I haven't checked if there are missing headers or anything like that).
Ah! That's good to hear!
Some minor comments:
* A complete build with unit tests took several hours on a Intel Core2 T7200 with 2GB ram and helped itself to a whopping 4.6GB of disk. Maybe a note could be added to the 'check' target in the Makefile stating that it will take a long time and requires approx 4.6 gigs of disk? (I started 'make check' before leaving my apartment just to come back later finding it had stopped halfway through because I'd ran out of diskspace)
Hum... Yes, it would be good to add a note.
* Docs are not installed. I would expect the docs to appear under $PREFIX/share/doc/boost-x.y/
That doesn't seem right to me either. Rene? Daniel?
* The headers are installed to $INCLUDEDIR/boost-1_35/boost, but I expected $INCLUDEDIR/boost. Supposing this is meant to enable parallel installs of different versions of boost I think this should be done using the --prefix option to configure, not hardcoded in the Jamfiles. (the static libraries and symlinks for the libs will be overwritten anyway if you attempt to install two versions to the same prefix).
Rene, is this your department? What do you think?
Other than that hings are looking good IMO, thanks for all your efforts to bring us a new release Beman!
It isn't just me. Rene Rivera, Daniel James, John Maddock, and many others have worked hard to both get this release out and to improve our infrastructure so that future releases will be smoother. And of course, thanks for your help too! --Beman
On Mon, Mar 24, 2008 at 08:36:36AM -0400, Beman Dawes wrote:
Tarjei Knapstad wrote:
* The headers are installed to $INCLUDEDIR/boost-1_35/boost, but I expected $INCLUDEDIR/boost. Supposing this is meant to enable parallel installs of different versions of boost I think this should be done using the --prefix option to configure, not hardcoded in the Jamfiles. (the static libraries and symlinks for the libs will be overwritten anyway if you attempt to install two versions to the same prefix).
Rene, is this your department? What do you think?
I'm not Rene, but I can maybe offer some insight here. By default, boost builds and installs with --layout=versioned, which will give you headers in ${PREFIX}/boost-x_xx/boost and the boost version number and compiler version embedded in the library names. If you want to have the old-fashioned ${PREFIX}/boost and less decorated library names, just pass --layout=system to bjam. I'm unsure if there's any analogous parameter to ./configure, but most likely not. In my not so humble opinion, I think that using configure/make/make install for boost is extraneous. By the way, what happened to the --build-type=minimal|complete option that the trunk has. Is that due for 1.35.1 or later? -- Lars Viklund | zao@acc.umu.se | 070-310 47 07
Lars Viklund wrote:
By the way, what happened to the --build-type=minimal|complete option that the trunk has. Is that due for 1.35.1 or later?
Arrg... I totally dropped the ball on that one. Beman, is OK to merge the Jamroot from trunk at this time? -- -- 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
Rene Rivera wrote:
Lars Viklund wrote:
By the way, what happened to the --build-type=minimal|complete option that the trunk has. Is that due for 1.35.1 or later?
Arrg... I totally dropped the ball on that one. Beman, is OK to merge the Jamroot from trunk at this time?
Yes, please go ahead. --Beman
Beman Dawes wrote:
Rene Rivera wrote:
By the way, what happened to the --build-type=minimal|complete option that the trunk has. Is that due for 1.35.1 or later? Arrg... I totally dropped the ball on that one. Beman, is OK to merge
Lars Viklund wrote: the Jamroot from trunk at this time?
Yes, please go ahead.
Done. -- -- 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
Beman Dawes wrote:
I should have asked not just for trouble reports, but success reports too.
I have successfully built rc2 on my Debian Linux box with gcc 4.1.3 - though I have probably not exercised it enough to detect any problems. A few notes, which are not things that need to be fixed for the release: - The top-level directory after untaring was called boost-posix-2008-03-21; I was expecting something more like boost-1.35.0-rc2; is this going to change for the final version? - It's nice that the build process uses "./configure; make; make install" but it would be even nicer if there was a file called INSTALL that explained, in a couple of lines, that that was the way to build it. This would make it even more like other open-source packages. - It looks as if configure checks for some dependencies (ICU?), but it didn't check whether I had the necessary python or bzip2 headers installed; it would be great if it could do this automatically. Regards, Phil.
Phil Endecott wrote:
Beman Dawes wrote:
I should have asked not just for trouble reports, but success reports too.
I have successfully built rc2 on my Debian Linux box with gcc 4.1.3 - though I have probably not exercised it enough to detect any problems.
A few notes, which are not things that need to be fixed for the release:
- The top-level directory after untaring was called boost-posix-2008-03-21; I was expecting something more like boost-1.35.0-rc2; is this going to change for the final version?
Yep. I picked that up too on a Windows install. I've added it to the issues list and will fix for RC3, which I hope is the final RC.
- It's nice that the build process uses "./configure; make; make install" but it would be even nicer if there was a file called INSTALL that explained, in a couple of lines, that that was the way to build it. This would make it even more like other open-source packages.
Would you like to volunteer to draft INSTALL? It should have two sections, one for POSIX-like systems, and one for Windows, and should also include a pointer to the full install docs. (Added to issues list, but not considered a showstopper.)
- It looks as if configure checks for some dependencies (ICU?), but it didn't check whether I had the necessary python or bzip2 headers installed; it would be great if it could do this automatically.
Doug, is this something you could look at? (Added to issues list, but not considered a showstopper.) Thanks for the report, Phil! --Beman
Beman Dawes wrote:
Phil Endecott wrote:
- It's nice that the build process uses "./configure; make; make install" but it would be even nicer if there was a file called INSTALL that explained, in a couple of lines, that that was the way to build it. This would make it even more like other open-source packages.
Would you like to volunteer to draft INSTALL? It should have two sections, one for POSIX-like systems, and one for Windows, and should also include a pointer to the full install docs. (Added to issues list, but not considered a showstopper.)
There are some good instructions at http://beta.boost.org/doc/libs/1_34_1/more/getting_started/unix-variants.htm..., section 5.1 "Easy Build and Install". That's for 1.34.1, and I've just been on a wild goose chase looking for the 1.35 equivalent. I can't find it at beta.boost.org, but I recall reading something here about the "more" content and beta.boost.org, so I won't revisit that. In the download, it seems to be in more/getting_started. That took me a _long_ time to find: I was doing all sorts of greps in the doc directory. Can't more be a subdir of doc? Or can't getting_started just live in doc? Having a bulging doc directory and then stashing the first documentation that you're going to need somewhere else just seems calculated to confuse. Anyway, here's what I propose putting in INSTALL in the root of the distribution. I don't know enough about Boost on Windows to write anything about that; feel free to edit. Installation Instructions ========================= Installation instructions can be found online at http://bost.org/???FIXME???/more/getting_started/. The same instructions can be found in the more/getting_started directory, once the documentation has been built. For the very impatient: on unix variants you can "./configure; make; make install". See the output of "./configure --help" for various settings that you may want to change. Phil.
Phil Endecott wrote:
There are some good instructions at http://beta.boost.org/doc/libs/1_34_1/more/getting_started/unix-variants.htm..., section 5.1 "Easy Build and Install". That's for 1.34.1, and I've just been on a wild goose chase looking for the 1.35 equivalent. I can't find it at beta.boost.org, but I recall reading something here about the "more" content and beta.boost.org, so I won't revisit that. In the download, it seems to be in more/getting_started. That took me a _long_ time to find: I was doing all sorts of greps in the doc directory.
Where the two links to the getting started docs not obvious from the boost-root/index.html file? Or is it the boost-root/index.html file itself?
Can't more be a subdir of doc? Or can't getting_started just live in doc? Having a bulging doc directory and then stashing the first documentation that you're going to need somewhere else just seems calculated to confuse.
True, but only if you are browsing around the files without reading the "front" page. Although integrating the getting started docs with the BoostBook docs is worth looking into. -- -- 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
Rene Rivera wrote:
Phil Endecott wrote:
There are some good instructions at http://beta.boost.org/doc/libs/1_34_1/more/getting_started/unix-variants.htm..., section 5.1 "Easy Build and Install". That's for 1.34.1, and I've just been on a wild goose chase looking for the 1.35 equivalent. I can't find it at beta.boost.org, but I recall reading something here about the "more" content and beta.boost.org, so I won't revisit that. In the download, it seems to be in more/getting_started. That took me a _long_ time to find: I was doing all sorts of greps in the doc directory.
Where the two links to the getting started docs not obvious from the boost-root/index.html file? Or is it the boost-root/index.html file itself?
I never noticed the index.html file in the root of the distribution. I'm not in the habit of browsing source-trees with a web browser. Phil.
Phil Endecott wrote:
Rene Rivera wrote:
Phil Endecott wrote:
There are some good instructions at http://beta.boost.org/doc/libs/1_34_1/more/getting_started/unix-variants.htm..., section 5.1 "Easy Build and Install". That's for 1.34.1, and I've just been on a wild goose chase looking for the 1.35 equivalent. I can't find it at beta.boost.org, but I recall reading something here about the "more" content and beta.boost.org, so I won't revisit that. In the download, it seems to be in more/getting_started. That took me a _long_ time to find: I was doing all sorts of greps in the doc directory. Where the two links to the getting started docs not obvious from the boost-root/index.html file? Or is it the boost-root/index.html file itself?
I never noticed the index.html file in the root of the distribution. I'm not in the habit of browsing source-trees with a web browser.
I think the best fix for this is to provide a very simple INSTALL file: See index.html for information about this release. The "Getting Started" section is a useful starting place. Comments? --Beman
Hello,
So if you downloaded RC2, please post a reply indicating what you've done with it, even if no problems or issues were detected. That way I can better gauge release readiness.
I compiled the RC2 with GCC 4.1.3 on Kubuntu and GCC 3.3.6 on Debian. All compiled well on GCC4 except for a few warnings. With GCC3, all compiled well too except Boost.Wave: it fails on a assertion in debug mode, and on a link error for release mode and dynamic link. Debug mode error: gcc.compile.c++ bin.v2/libs/wave/build/gcc-3.3.6 /debug/threading-multi/instantiate_cpp_exprgrammar.o In file included from boost/wave/wave_config.hpp:201, from libs/wave/src/instantiate_cpp_exprgrammar.cpp:11: boost/wave/util/flex_string.hpp: In member function `void boost::wave::util::AllocatorStringStorage<E, A>::append(ForwardIterator, ForwardIterator)': boost/wave/util/flex_string.hpp:709: error: syntax error before `;' token boost/wave/util/flex_string.hpp:709: error: syntax error before `;' token [...] Release mode link error: `.L520' referenced in section `.rodata' of bin.v2 /libs/serialization/build/gcc-3.3.6/debug/threading-multi/text_iarchive.o: defined in discarded section `.gnu.linkonce.t._ZNK5boost7archive17archive_exception4whatEv' of bin.v2 /libs/serialization/build/gcc-3.3.6/debug/threading-multi/text_iarchive.o [...] You can find the whole output in attachment for both compilers. Regards Bruno
So if you downloaded RC2, please post a reply indicating what you've done with it, even if no problems or issues were detected. That way I can better gauge release readiness.
I compiled the RC2 with GCC 4.1.3 on Kubuntu and GCC 3.3.6 on Debian. All compiled well on GCC4 except for a few warnings. With GCC3, all compiled well too except Boost.Wave: it fails on a assertion in debug mode, and on a link error for release mode and dynamic link.
Debug mode error:
gcc.compile.c++ bin.v2/libs/wave/build/gcc-3.3.6 /debug/threading- multi/instantiate_cpp_exprgrammar.o In file included from boost/wave/wave_config.hpp:201, from libs/wave/src/instantiate_cpp_exprgrammar.cpp:11: boost/wave/util/flex_string.hpp: In member function `void boost::wave::util::AllocatorStringStorage<E, A>::append(ForwardIterator, ForwardIterator)': boost/wave/util/flex_string.hpp:709: error: syntax error before `;' token boost/wave/util/flex_string.hpp:709: error: syntax error before `;' token [...]
This is caused by an assertion construct apparently not understood by some compilers. I removed this assertion for now. Everything should compile from now on.
Release mode link error:
`.L520' referenced in section `.rodata' of bin.v2 /libs/serialization/build/gcc-3.3.6/debug/threading- multi/text_iarchive.o: defined in discarded section `.gnu.linkonce.t._ZNK5boost7archive17archive_exception4whatEv' of bin.v2 /libs/serialization/build/gcc-3.3.6/debug/threading- multi/text_iarchive.o [...]
This is now a Wave problem, but some platform specific bug. Regards Hartmut
Hartmut Kaiser wrote:
So if you downloaded RC2, please post a reply indicating what you've done with it, even if no problems or issues were detected. That way I can better gauge release readiness.
I compiled the RC2 with GCC 4.1.3 on Kubuntu and GCC 3.3.6 on Debian. All compiled well on GCC4 except for a few warnings. With GCC3, all compiled well too except Boost.Wave: it fails on a assertion in debug mode, and on a link error for release mode and dynamic link.
Debug mode error:
gcc.compile.c++ bin.v2/libs/wave/build/gcc-3.3.6 /debug/threading- multi/instantiate_cpp_exprgrammar.o In file included from boost/wave/wave_config.hpp:201, from libs/wave/src/instantiate_cpp_exprgrammar.cpp:11: boost/wave/util/flex_string.hpp: In member function `void boost::wave::util::AllocatorStringStorage<E, A>::append(ForwardIterator, ForwardIterator)': boost/wave/util/flex_string.hpp:709: error: syntax error before `;' token boost/wave/util/flex_string.hpp:709: error: syntax error before `;' token [...]
This is caused by an assertion construct apparently not understood by some compilers. I removed this assertion for now. Everything should compile from now on.
Good. Thanks, --Beman
At 11:25 AM +0100 3/25/08, Bruno Lalande wrote:
I compiled the RC2 with GCC 4.1.3 on Kubuntu and GCC 3.3.6 on Debian. All compiled well on GCC4 except for a few warnings. With GCC3, all compiled well too except Boost.Wave: it fails on a assertion in debug mode, and on a link error for release mode and dynamic link.
Debug mode error: [...]
Release mode link error:
`.L520' referenced in section `.rodata' of bin.v2 /libs/serialization/build/gcc-3.3.6/debug/threading-multi/text_iarchive.o: defined in discarded section `.gnu.linkonce.t._ZNK5boost7archive17archive_exception4whatEv' of bin.v2 /libs/serialization/build/gcc-3.3.6/debug/threading-multi/text_iarchive.o [...]
Is the release mode link error an actual error, or just (un)informative messages being printed by the linker. This looks like http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16625 which was fixed in gcc 4.1. We saw these same messages when using some versions of gcc 3.3.x on some distributions, but were never able to assign any actual problem to anything related to this. That is, so far as we could tell these messages look scary but may actually be harmless.
Hi, There is a documentation error in libs/type_traits/doc/html/boost_typetraits/category/function.html template <std::size_t Align> struct function_traits; must be template <class T> struct function_traits; Regards _____________________ Vicente Juan Botet Escriba ----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: "Boost mailing list" <boost@lists.boost.org>; "Boost Users mailing list" <boost-users@lists.boost.org> Sent: Friday, March 21, 2008 1:42 PM Subject: [boost] [1.35.0] Release Candidate 2 available
1.35.0 Release Candidate 2 (RC2) is available at http://boost.cowic.de/rc/ RC2 fixes all of the serious issues reported for RC1.
Note that links to the web site from the RC appear to be broken because the restructured web site will not go live until the actual release ships. In the meantime, the new website content is available at beta.boost.org.
Please take the time to download RC2, and try to install it on your system. Kick the tires, and report any problems or issues you discover. Report by posting to either boost@lists.boost.org or boost-users@lists.boost.org.
For a list of known issues, see http://svn.boost.org/trac/boost/wiki/MergeOneDotThreeFiveDotZero.
Thanks,
--Beman
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
vicente.botet wrote:
Hi,
There is a documentation error in libs/type_traits/doc/html/boost_typetraits/category/function.html
template <std::size_t Align> struct function_traits;
must be template <class T> struct function_traits;
Regards _____________________ Vicente Juan Botet Escriba
Sounds like an issue for John Maddock. John? Thanks for the report, --Beman
participants (9)
-
Beman Dawes -
Bruno Lalande -
Hartmut Kaiser -
Kim Barrett -
Lars Viklund -
Phil Endecott -
Rene Rivera -
Tarjei Knapstad -
vicente.botet