Proposal: Post-Release Maintenance Team (WAS Re: [test] [gcc-4.3.2] check_is_close and check_is_small issues)
On Thu, Feb 19, 2009 at 3:58 PM, Juergen Hunold <juergen.hunold@ivembh.de> wrote:
Hi Dean !
On Thursday 19 February 2009 02:34:05 Dean Michael Berris wrote:
Thanks for these links! Did they apply cleanly to Boost 1.38.0 for you? I tried both (in the given order above) and I got some rejections when I applied them to a cleanly unpacked distribution.
Well, actually not ;-(( I think you can safely ignore the patch to utils/runtime/cla/parameter.hpp as this just fixes a regression which happened in between the changes. I'll dig further into this and ask the maintainer for permission to merge at least the warning fixes to the release branch.
Alright. Now this time, would there be any objections if I (or other people) tried managing a patch release for 1.38.0? Would anybody else be interested in helping release a 1.38.1 with fixes hand-ported from trunk to 1.38.0? I've found some Jamfile fixes required to work around the (I'm guessing, now defunct) 'message' function in Boost.Build v2 that's bundled with Boost 1.38 that might be worth looking at. I'm also interested in bringing in a newer version of Boost.Build from the nightly builds into the 1.38.0 release to be packaged as 1.38.1; HTH -- Dean Michael Berris | Software Engineer, Friendster, Inc. blog.cplusplus-soup.com | twitter.com/mikhailberis | linkedin.com/in/mikhailberis | profiles.friendster.com/mikhailberis | deanberris.com
Dean Michael Berris wrote:
On Thu, Feb 19, 2009 at 3:58 PM, Juergen Hunold <juergen.hunold@ivembh.de> wrote:
Hi Dean !
On Thursday 19 February 2009 02:34:05 Dean Michael Berris wrote:
Thanks for these links! Did they apply cleanly to Boost 1.38.0 for you? I tried both (in the given order above) and I got some rejections when I applied them to a cleanly unpacked distribution.
Well, actually not ;-(( I think you can safely ignore the patch to utils/runtime/cla/parameter.hpp as this just fixes a regression which happened in between the changes. I'll dig further into this and ask the maintainer for permission to merge at least the warning fixes to the release branch.
Alright.
Now this time, would there be any objections if I (or other people) tried managing a patch release for 1.38.0? Would anybody else be interested in helping release a 1.38.1 with fixes hand-ported from trunk to 1.38.0?
I've found some Jamfile fixes required to work around the (I'm guessing, now defunct) 'message' function in Boost.Build v2 that's bundled with Boost 1.38 that might be worth looking at.
I don't understand what you're saying, sorry. The 'message' function is fine as far as I'm concerned -- what "work arounds" do you have in mind and for what purpose? - Volodya
On Thu, Feb 19, 2009 at 4:18 PM, Vladimir Prus <vladimir@codesourcery.com> wrote:
Dean Michael Berris wrote:
I've found some Jamfile fixes required to work around the (I'm guessing, now defunct) 'message' function in Boost.Build v2 that's bundled with Boost 1.38 that might be worth looking at.
I don't understand what you're saying, sorry. The 'message' function is fine as far as I'm concerned -- what "work arounds" do you have in mind and for what purpose?
So apparently since I upgraded from Boost 1.35.0 to 1.38.0, what used to build fine for me (since I used Boost.Build v2 as well in my projects) when I referred to them by name (/boost//regex and /boost//graph), Boost.Jam complained that it couldn't find a rule for 'message'. So instead of using 'message' I changed them to use ECHO instead directly. I don't know if this is the right solution, but since I encountered the issue on my own I thought I'd work around it on my setup. This got the build working fine for me at least. I'm not sure if this is an issue at a bigger scale, but just as well I figure it might help others too. HTH -- Dean Michael Berris | Software Engineer, Friendster, Inc. blog.cplusplus-soup.com | twitter.com/mikhailberis | linkedin.com/in/mikhailberis | profiles.friendster.com/mikhailberis | deanberris.com
Dean Michael Berris wrote:
On Thu, Feb 19, 2009 at 4:18 PM, Vladimir Prus <vladimir@codesourcery.com> wrote:
Dean Michael Berris wrote:
I've found some Jamfile fixes required to work around the (I'm guessing, now defunct) 'message' function in Boost.Build v2 that's bundled with Boost 1.38 that might be worth looking at.
I don't understand what you're saying, sorry. The 'message' function is fine as far as I'm concerned -- what "work arounds" do you have in mind and for what purpose?
So apparently since I upgraded from Boost 1.35.0 to 1.38.0, what used to build fine for me (since I used Boost.Build v2 as well in my projects) when I referred to them by name (/boost//regex and /boost//graph), Boost.Jam complained that it couldn't find a rule for 'message'.
So instead of using 'message' I changed them to use ECHO instead directly.
This means that you are using Boost 1.38.0 together with and older copy of Boost.Build. Use --debug-configuration to check if that's the case -- it will print the location where Boost.Build is found. - Volodya
participants (2)
-
Dean Michael Berris -
Vladimir Prus