
Steven Watanabe has recently reported that a bug in Boost.Build caused boost libraries to be rebuilt when bjam is invoked again after a successful build. This affects msvc. I've just now reproduced and fixed this on trunk: https://svn.boost.org/trac/boost/changeset/55717 Since this fairly annoying behaviour, I would like to merge it to release branch. OK? I'd expect at least on trunk msvc tester to cycle shortly, so I should be able to merge tomorrow morning. Thanks, Volodya

Vladimir Prus wrote:
Steven Watanabe has recently reported that a bug in Boost.Build caused boost libraries to be rebuilt when bjam is invoked again after a successful build. This affects msvc. I've just now reproduced and fixed this on trunk:
https://svn.boost.org/trac/boost/changeset/55717
Since this fairly annoying behaviour, I would like to merge it to release branch. OK? I'd expect at least on trunk msvc tester to cycle shortly, so I should be able to merge tomorrow morning.
Ping? There are now trunk test result for msvc, with a later revision, nothing unexpected. - Volodya

Vladimir Prus wrote:
Vladimir Prus wrote:
Steven Watanabe has recently reported that a bug in Boost.Build caused boost libraries to be rebuilt when bjam is invoked again after a successful build. This affects msvc. I've just now reproduced and fixed this on trunk:
https://svn.boost.org/trac/boost/changeset/55717
Since this fairly annoying behaviour, I would like to merge it to release branch. OK? I'd expect at least on trunk msvc tester to cycle shortly, so I should be able to merge tomorrow morning.
Ping? There are now trunk test result for msvc, with a later revision, nothing unexpected.
Oops, I thought I replied already. Sorry. Yes, if all looks good on trunk then go ahead with the merge. -- Eric Niebler BoostPro Computing http://www.boostpro.com

Eric Niebler wrote:
Vladimir Prus wrote:
Vladimir Prus wrote:
Steven Watanabe has recently reported that a bug in Boost.Build caused boost libraries to be rebuilt when bjam is invoked again after a successful build. This affects msvc. I've just now reproduced and fixed this on trunk:
https://svn.boost.org/trac/boost/changeset/55717
Since this fairly annoying behaviour, I would like to merge it to release branch. OK? I'd expect at least on trunk msvc tester to cycle shortly, so I should be able to merge tomorrow morning.
Ping? There are now trunk test result for msvc, with a later revision, nothing unexpected.
Oops, I thought I replied already. Sorry. Yes, if all looks good on trunk then go ahead with the merge.
Thank you. The change is merged now. - Volodya
participants (3)
-
Eric Niebler
-
Vladimir Prus
-
Vladimir Prus