[1.37.0] pre-beta snapshot available
The boost-posix and boost-windows snapshots of what will become the 1.37.0 beta are available. See http://boost.cowic.de/rc/ It would be helpful to get confirmation that these look OK. Past snapshots, betas, and release had been built on a Windows system, but 1.37.0 is being built on a Linux system to try to avoid doc build problems that plague the Windows variant. As always, separate svn exports are done, requesting the appropriate line endings, but I'd still like more eyeballs on this to make sure all is well. I'd specifically like confirmation from Eric and Daniel that the built docs look OK. If all is well, I'll build the beta tomorrow. In the meantime, no branches/release commits, please. Thanks, --Beman
2008/10/20 Beman Dawes <bdawes@acm.org>:
I'd specifically like confirmation from Eric and Daniel that the built docs look OK.
The Xpressive chapter is missing. There's a red '<xi:include></xi:include>' at the bottom of 'doc/html/libraries.html' which I guess is from a failed attempt at including it. Are there any errors in the build log? Daniel
On Mon, Oct 20, 2008 at 3:58 PM, Daniel James <daniel_james@fmail.co.uk>wrote:
2008/10/20 Beman Dawes <bdawes@acm.org>:
I'd specifically like confirmation from Eric and Daniel that the built
docs
look OK.
The Xpressive chapter is missing. There's a red '<xi:include></xi:include>' at the bottom of 'doc/html/libraries.html' which I guess is from a failed attempt at including it. Are there any errors in the build log?
Approximately 1200. That's one of the doc builds many problems; it flags so many things as "error" that the uninitiated can't tell the difference between a real error and the cruft. I've sent you the log via private email. --Beman
2008/10/20 Beman Dawes <bdawes@acm.org>:
Approximately 1200. That's one of the doc builds many problems; it flags so many things as "error" that the uninitiated can't tell the difference between a real error and the cruft.
I've sent you the log via private email.
It's easier than interpreting your average C++ template error: daniel@bah ~> grep -i error posix-bjam.log | grep -i xpressive Preprocessing /home/beman/snapshot/posix/boost/xpressive/regex_error.hpp... Parsing file /home/beman/snapshot/posix/boost/xpressive/regex_error.hpp... Generating code for file /home/beman/snapshot/posix/boost/xpressive/regex_error.hpp... Generating docs for file /home/beman/snapshot/posix/boost/xpressive/regex_error.hpp... Generating docs for compound boost::xpressive::regex_error... Generating XM/home/beman/snapshot/posix/boost/xpressive/regex_error.hpp:48: Warning: The following parameters of boost::xpressive::regex_error::regex_error(regex_constants::error_type code, char const *str="") are not documented: Generating XML output for class boost::xpressive::regex_error /home/beman/snapshot/posix/libs/xpressive/doc/static_regexes.qbk:144: error: Syntax Error near column 51. /home/beman/snapshot/posix/libs/xpressive/doc/static_regexes.qbk:145: error: Syntax Error near column 53. /home/beman/snapshot/posix/libs/xpressive/doc/static_regexes.qbk:146: error: Syntax Error near column 53. This seems to be a problem with the new 'globalref' tag. I'm looking into it. But quickbook should return an error code when there's a syntax error so that the build fails. I'll look into implementing that soon. Daniel
Daniel James wrote:
This seems to be a problem with the new 'globalref' tag. I'm looking into it.
But quickbook should return an error code when there's a syntax error so that the build fails. I'll look into implementing that soon.
This could be a problem if Beman is using an old, prebuilt quickbook executable that doesn't have the new support for globalref. Beman? -- Eric Niebler BoostPro Computing http://www.boostpro.com
On Mon, Oct 20, 2008 at 6:25 PM, Daniel James <daniel_james@fmail.co.uk>wrote:
2008/10/20 Eric Niebler <eric@boost-consulting.com>:
This could be a problem if Beman is using an old, prebuilt quickbook executable that doesn't have the new support for globalref. Beman?
That was it, we worked it out in the end.
The snapshot has been refreshed. See http://boost.cowic.de/rc/ The doc/html/libraries.html looks OK to me, but others should also check. The links work, too. --Beman
Beman Dawes wrote:
On Mon, Oct 20, 2008 at 6:25 PM, Daniel James <daniel_james@fmail.co.uk>wrote:
2008/10/20 Eric Niebler <eric@boost-consulting.com>:
This could be a problem if Beman is using an old, prebuilt quickbook executable that doesn't have the new support for globalref. Beman? That was it, we worked it out in the end.
The snapshot has been refreshed. See http://boost.cowic.de/rc/
The doc/html/libraries.html looks OK to me, but others should also check. The links work, too.
Are you still running the script which compares trunk and branches/release? That should have picked up some unmerged changes in libs/dynamic_bitset. I'll have to fix this :-( -- Genny
On Tue, Oct 21, 2008 at 7:08 AM, Gennaro Prota <gennaro.prota@yahoo.com>wrote:
Beman Dawes wrote:
On Mon, Oct 20, 2008 at 6:25 PM, Daniel James <daniel_james@fmail.co.uk
wrote:
2008/10/20 Eric Niebler <eric@boost-consulting.com>:
This could be a problem if Beman is using an old, prebuilt quickbook executable that doesn't have the new support for globalref. Beman?
That was it, we worked it out in the end.
The snapshot has been refreshed. See http://boost.cowic.de/rc/
The doc/html/libraries.html looks OK to me, but others should also check. The links work, too.
Are you still running the script which compares trunk and branches/release? That should have picked up some unmerged changes in libs/dynamic_bitset.
No. Too many false positives. Also, this is the third release where developers must merge trunk changes into branches/release if they are to appear in the release. Developers are hopefully getting used to that procedure. --Beman
Beman Dawes wrote:
Are you still running the script which compares trunk and branches/release? That should have picked up some unmerged changes in libs/dynamic_bitset.
No. Too many false positives.
Also, this is the third release where developers must merge trunk changes into branches/release if they are to appear in the release. Developers are hopefully getting used to that procedure.
First one for me :-) But that's not the point... I think I merged --issued the command, that is-- from libs/dynamic_bitset; yet some files therein are identical, some others aren't. I'll have to look into it. -- Genny
Beman Dawes wrote:
I'd specifically like confirmation from Eric and Daniel that the built docs look OK.
If all is well, I'll build the beta tomorrow. In the meantime, no branches/release commits, please.
I checked the .7z file and the docs look good. The formulas in the accumulators docs came out ok, which is always the test. I noticed one small problem ... in doc/html/index.html, Boost.Xpressive is not listed. It is there in 1.36. There is something fishy here because the stub doc/html/xpressive.html should have been overwritten during the doc build process but it wasn't. As a result, any link to xpressive's documentation gets redirected to: http://www.boost.org/regression-logs/cs-win32_metacomm/doc/html/xpressive.ht... That's a dead link. I don't know why only xpressive seems to have this problem, but I don't have the time to investigate right now. :-( -- Eric Niebler BoostPro Computing http://www.boostpro.com
participants (4)
-
Beman Dawes -
Daniel James -
Eric Niebler -
Gennaro Prota