vicente.botet wrote:
----- Original Message ----- From: "Vladimir Prus" <vladimir@codesourcery.com> To: <boost@lists.boost.org> Sent: Monday, June 07, 2010 12:05 PM Subject: [boost] [trac] "Building Boost" vs. "build"
It looks like somebody went via Trac and moved some issues from the "Building Boost" component to "build" component. See, for example:
https://svn.boost.org/trac/boost/ticket/4147
I certainly appreciate help with triaging issues, but in general, such change seems wrong -- "Building Boost" is for issues affecting exactly that -- building boost, while the 'build' component contain issues that are not necessary affecting Boost C++ Libraries at all.
Unfortunately, the changes are all anonymous, so it would be great if whoever made them speak up, and discuss the rationale.
Hi,
Sorry if I was wrong while changing the library?
I recognize I was wrong changing #4147. Let me know if I must revert the change for the other. #3625 python detection randomly broken #3904 installing boost 1.42 does not update all include files in the destination directory #4243 darwin.jam: -mmacosx-version-min not passed to compiler #3993 target-os=linux should imply threadapi=posix
I think that #3904 appears to manifest on Boost itself, too. Also, #3993 objects to behaviour of Boost.Thread Jamfiles.
BTW. I though that I was logged in.
Did you login, or just enter your name when submitting a change? In the latter case, the name is forgotten and must be entered again when editing next issue. - Volodya