- Boost - lists.boost.org

dll-path feature
by brook＠biology.nmsu.edu 01 Aug '08

01 Aug '08

It seems that I need to use the dll-path feature to add an -rpath directive to the linker when my boost libraries are installed. This seems to be described (mostly) fairly clearly at http://www.boost.org/boost-build2/doc/html/bbv2/faq/dll-path.html What is not clear is where the feature should be invoked. My attempt to modify Jamroot to add <dll-path> to the boost-install rule failed in the sense that not rpath information makes it into the installed libraries. (The rest of this snippet is the original.). rule boost-install ( libraries * ) { package.install install : <dependency>/boost//install-headers $(install-requirements) : # No binaries : $(libraries) : # No headers, it's handled by the dependency ; install stage : $(libraries) : <location>$(BOOST_STAGE_LOCATE) <dll-path>/path/to/add/via/rpath ; local c = [ project.current ] ; local project-module = [ $(c).project-module ] ; module $(project-module) { explicit stage ; explicit install ; } } So, how is one supposed to invoke the <dll-path> feature in order to have -rpath added to the linking of libraries during their installation? Thanks for your help. Cheers, Brook

3 4

[1.36.0 beta] Bug fix procedures
by Beman Dawes 01 Aug '08

01 Aug '08

Bug reports from the beta are starting to surface on the user's list. Here is the procedure for dealing with them: * Apply the fix to the trunk. * Wait until enough regression tests have cycled to demonstrate that the fix worked and didn't break anything else. * Apply the fix to branches/release. * Keep an eye on the release test results to be sure there were no unintended consequences. In other words, there is no need to ask the release managers for permission to apply to branches/release as long as tests are clean. The whole point of doing a beta is to shake these user detected bugs out of the woodwork and apply the resulting fixes in time for the release. Thanks, --Beman

3 2

fixed-pt [improved]
by Neal Becker 01 Aug '08

01 Aug '08

Here is an improved version of fixed-pt, incorporating some of the suggestions given here:

5 4

[release] xpressive bug fix
by Eric Niebler 01 Aug '08

01 Aug '08

What are the chances that I'll be able to merge a bug fix to the release branch? This one: http://svn.boost.org/trac/boost/ticket/2157 just came in, and I've already fixed it on trunk. Assuming that the next cycle of the trunk tests don't show anything amiss, would I be permitted to merge the fix? The bug will not cause crashes, but it will lead to incorrect results when matching the end-of-line assertion ($) against internal line breaks, which is fairly common usage scenario. I have high confidence in the fix. These are the relevant changesets: http://svn.boost.org/trac/boost/changeset/47899 http://svn.boost.org/trac/boost/changeset/47901 -- Eric Niebler BoostPro Computing http://www.boostpro.com

2 3

1.36 documentation
by Daniel James 01 Aug '08

01 Aug '08

Hello everyone, Since the generated documentation isn't currently included in the snapshots, I've temporarily made it available here: http://www.calamity.org.uk/1.36/ Hopefully, the documentation should be integrated with the beta site soon after the beta release. Daniel

9 19

[swap] End-user allowed to add overloads to boost namespace?
by Niels Dekker - mail address until 2008-12-31 31 Jul '08

31 Jul '08

Is any end-user allowed to add her own overloads of existing Boost functions to the boost namespace? The boost::swap utility from Joseph Gauterin (recently moved to the trunk) allows the user to customize boost::swap for her class, by providing a swap function for her class within the namespace of the class. Internally boost::swap does the idiomatical "using std::swap; swap(left,right);", to allow finding such a user-provided swap function by argument-dependent lookup (ADL) <svn.boost.org/svn/boost/trunk/boost/utility/swap.hpp> Unfortunately some compilers don't fully supported ADL, as is shown by the mixed test results of swap/test/specialized_in_global.cpp and swap/test/specialized_in_other.cpp, at http://www.boost.org/development/tests/trunk/developer/utility-swap_.html ADL failures appear to occur for GCC 3.3.1 (PathScale), Intel C++ 8.1, MSVC 7.1 (2003), and Borland (up to 5.9.3). Once the boost::swap utility would be used by other Boost libraries, end users might want to add a custom overload of swap for their classes to the boost namespace. Especially when users would have to deal with lacking ADL support of their compiler. Would it be okay for them to do so? Or are there some moral objections, or technical issues, regarding a user-provided overload within the boost namespace? Kind regards, Niels PS Volodya, thanks for fixing swap/Jamfile.v2! -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center

6 14

boost versus Apple's gcc 4.2
by Mat Marcus 31 Jul '08

31 Jul '08

On the boost users list, there was a discussion about some issues arising with boost versus gcc-4.2 on Apple systems. One interesting issue arises from the fact that Apple decoupled the gcc compiler version from the lib version. They "own" libstdc++, which they've kept at version 4.0 even when the 4.2 compiler. This breaks some assumptions in boost headers. I am reposting on the main developer list: ### Peter Dimov wrote: > Is the new Apple GCC documented somewhere? I wasn't able to find anything > related to a new assembler syntax or -fasm-blocks. Can you ask Apple to > explain the issue? Stock g++ 4.2.x compiles the code, so the problem must be > Apple-specific. Ok, I've got a little bit more information on the Apple gcc 4.2 situation. Here is a snippet from an email dialog between a user and an apple compiler engineer: user appears below with with prefix ">>" apple compiler engineer appears below with with prefix ">" >> Thank you very much for the detailed reply. >> Based on your information I deduce: >> >> 1) Using gcc 4.2 with 4.0 (c++) libraries is a supported >> configuration by Apple > > Right. > >> I then conclude that the C++ ABI is fully compatible between 4.0 and >> 4.2 > > Right. [snip, then user hypothesizes as to why there are problems with boost under gcc 4.2/libstdc++ 4.0 on current Apple systems] >> This is the case because boost assumes that a 4.2 compiler implies >> 4.2 libraries in flies such as boost/detail/atomic_count_gcc.hpp: >> >> #if (__GNUC__ > 4) || ((__GNUC__ == 4) && (__GNUC_MINOR__ >= 2)) >> # include <ext/atomicity.h> >> #else >> # include <bits/atomicity.h> >> #endif > > Yes, this is a bug or faulty assumption in boost. [snip] > The 4.2 library issue is a bug in Boost, not a problem with > our compiler. I'd suggest raising the issue on one of the boost > mailing lists and see what they say. Comments? Mat

4 4

[1.36 beta] Beta release candidate available
by Beman Dawes 31 Jul '08

31 Jul '08

Release candidate tarballs for the 1.36 beta are available at http://boost.cowic.de/rc/ Special thanks to Daniel James for generating the docs. Hopefully we can get the doc generations problems fixed quickly so that we can get back on a nightly release snapshot generation running again. I'd like to get feedback before uploading these to SourceForge. Please post a reply indicating success or problems encountered, being sure to indicate your platform and which file you downloaded. Thanks, --Beman

5 8

The --toolset option
by Vladimir Prus 31 Jul '08

31 Jul '08

Okay, now it's my turn to propose something to sneak into 1.36.0 at the last minute. Fortunately, it's only documentation change. For quite a while, both getting-started, and bjam --help mentioned --toolset option. This in practice, resulted in folks getting wrong analogy and trying to use --variant=debug --link=shared, etc. We agreed (on Boost.Build list), in principle, that we better remove --toolset from documentation, and use 'toolset=' instead -- which has exactly the same effect. So, I would like to commit the following Jamroot change to HEAD and merge to release branch. Any objections? I also would like to see the issue filed against getting-started: http://svn.boost.org/trac/boost/ticket/2050 fixed, and can provide a patch assuming release manager is fine with having this doc tweak merged into release branch, too. Opinions? Thanks, Volodya

3 2

range_ex: status?
by Mathias Gaunard 30 Jul '08

30 Jul '08

I'm writing some piece of software working that does a lot of data structures traversal and that really needed filtering of traversal etc. I thought I'd get that from Boost.Range, but I was surprised to see Boost.Range provides very little: all the good stuff (the range-based algorithms and adaptors) are in another library, range_ex, which isn't in the main distribution yet. Will this library be included in Boost soon? It's really great. As for the open issues, here are my opinions: - Output ranges: don't adaptors already output ranges? - Two input ranges, or a range and an iterator?: two ranges can do more - For any algorithm foo(container, args...), if foo(args...) is valid then it should be called - Null-termination of C-style strings: Isn't that up to Boost.Range to decide whether it's a range or not?

18 104