- Boost - lists.boost.org

Re: [boost] [1.34.0-beta][Build] Problems with stagedir option
by Johannes Brunen 08 May '07

08 May '07

Thank, you. I missed this: Usage: bjam [options] [install|stage] Regards, Johannes "Eoin O'Callaghan" <eoinoc(a)iol.ie <mailto:eoinoc@iol.ie>> schrieb im Newsbeitrag <news:46403B24.5070308@iol.ie>...> Johannes Brunen wrote: >> Hi, >> >> today I tried building the beta version on win XP (VC 7.1) with the >> following bjam call: >> >> bjam --libdir=./stage --stagedir=./stage release debug threading=multi >> > > I think you just also need to add 'stage' to the commandline > > bjam --libdir=./stage --stagedir=./stage release debug threading=multi stage > > Regards, Eoin > > > _______________________________________________ > Unsubscribe & other changes: <http://lists.boost.org/mailman/listinfo.cgi/boost> >

1 0

[1.34.0-beta][Build] Problems with stagedir option
by Johannes Brunen 08 May '07

08 May '07

Hi, today I tried building the beta version on win XP (VC 7.1) with the following bjam call: bjam --libdir=./stage --stagedir=./stage release debug threading=multi All libraries build fine. However, the stagedir option seems not to work properly (in case I used it correctly). None of the libraries got copied to the ./stage directory, which I had created beforehand. Additionally, I tried bjam --stagedir=./stage release debug threading=multi with the same result. The following call bjam --version gives Boost.Build V2 (Milestone 11) Boost.Jam 03.1.14 Is there any usage failure on my side or is this an undiscoverd problem. With best regards, Johannes Brunen DataSolid GmbH

2 1

[1.34.0].[Solaris 10] Build failure
by Prashant Thakre 08 May '07

08 May '07

Hi, I am trying to build boost_1_34_0 on Solaris 10 using Sun C++ 5.8. Sun C++ 5.8 requires "-library=stlport4" for successful build of boost_1_34_0. However, by default bjam is using the standard library. How do I pass <stdlib>sun-stlport option at command line ? Currently the only way (as per the instructions @ http://blogs.sun.com/sga/ category/Boost ) is to create user-config.jam with following contents --------------------------------cut here---------------------------------- import toolset : using ; using sun : : /db2/sunstudio11/SUNWspro/bin/CC : <cxxflags>-library=stlport4 <cxxflags>-features=tmplife <cxxflags>-features=tmplrefstatic <linkflags>-library=stlport4 ; --------------------------------cut here---------------------------------- regards, Prashant Thakre

1 0

ADT Problem on gcd() in rational.hpp
by shinyee 08 May '07

08 May '07

Hi, I found rational.hpp uses both gcd(x,y) and gcd<IntType>(x,y). It causes name clashes with the gcd() function in my namespace. Would be more error free by using gcd<IntType>(x,y) throughout? Anyone can advise? See http://groups.google.com/group/comp.lang.c++/browse_thread/thread/23e9bb515… Regards, Shin Yee

1 0

[Probability] interest in probability/likelihood library
by Brook Milligan 08 May '07

08 May '07

This note is to announce the release of a library for handling probability and likelihood quantities, together with their logarithms, in a consistent and (when desired) transparent manner. Ultimately, I think this could be useful to the Boost community (e.g., it may find application within the recently reviewed math toolkit or be useful together with the recently accepted units library, from which it draws certain ideas). I would however appreciate feedback on that point, as well as on ways to improve its design, implementation, or documentation. What follows is an overview, and an indication of a couple of areas I know I need help with. More information is also available at http://biology.nmsu.edu/software/probability The code may be downloaded at ftp://biology.nmsu.edu/pub/software/probability/probability-0.1.tar.gz OVERVIEW As you know, both probabilities and likelihoods recur throughout statistical models. Consequently, those quantities must be represented by the type system in computational statistical models. Commonly, this is done by using a suitable native floating point type (e.g., double). One specific drawback with this approach is that the compiler cannot enforce the correct usage of types and confusion may arise between probabilities/likelihoods and other floating point types. More insidious, however, is the confusion likely to arise when the computations involve both these quantities and their logarithms. Indeed, the solution to many statistical models involves logarithms of probabilities and likelihoods more than the natural quantities. However, models that require both are not uncommon. If a native floating point type is used for probabilities and likelihoods, the programmer must not only distinguish those from other floating point quantities (e.g., parameters), but also must distinguish them from their logarithms. Subtle mistakes easily result from forgetting which domain (linear or logarithm) a quantity refers to. Much clearer code would result if the following syntax were available to express the intents that (i) the likelihood should be calculated as a product across independent observations, and (ii) it should be accumulated using logarithms to avoid underflow. probability poisson (unsigned int i); // probability model log_likelihood l; // product of likelihoods across a series of independent observations for (observations::const_iterator i = obs.begin(); i != obs.end(); ++i) l *= poisson(*i); The purpose of this library is to encapsulate both probability and likelihood quantities within an appropriate set of types, while simultaneously achieving the following design goals. - Provide both convenient default and more flexible advanced types for representing all probability and likelihood quantities. - Maintain type safety between probabilities and likelihoods, and between their corresponding native quantities and logarithms. - Incur no runtime cost. That is, all type manipulations should be performed at compile time. - Impose no limitations on the type used to represent the value of a probability or likelihood, beyond the obvious requirement that it models a real number within a suitable domain. - Ensure that the layout of arrays and structures of probability and likelihood quantities is identical to the corresponding layout for the underlying value type. - Verify the validity of probability values within the closed domain [0,1] and likelihood values within the closed domain [0,infinity], both as native quantities and as logarithms. - Support the validator concept to allow either complete removal of the validation checks, thereby eliminating their run-time cost, or replacement with an alternative. - Provide all appropriate arithmetic operations, while limiting implicit type conversions to those absolutely necessary and naturally expected. - Provide consistent semantics for the arithmetic operations in terms of their definitions for native quantities in the linear domain. One consequence of this is that in many contexts the quantities can be regarded simply as probabilities or likelihoods without respect to their representational domain. Another important consequence is that generic algorithms may be constructed based on a common set of operators that retain their semantics across the representational domains. Given these design goals, when the types provided by the library are used the compiler can enforce type safety, provide conversions as required. and guarrantee that the intent is directly expressed in the source code. Furthermore, any type that models a real number may be used as the value type for probabilities and likelihoods. If a double is sufficient, however, the simple default types make the task of instantiating these quantities easier. AREAS NEEDING ASSISTANCE The following are a few items I can identify that I need assistance with. - Compiler specifics: This is thoroughly tested with g++ (v3 and v4), but I need information on its portability. - The test cases seem to require BOOST_TEST_DONT_PRINT, even though stream operators are present. Although the current code works, it seems incorrect to require that macro. - Some tests cannot use BOOST_CHECK_EQUAL when they otherwise seem like they should. The problem appears to be an interaction with the printing of test cases and may be related to the previous item. - Being new to the Boost community, I am unfamiliar with how to incorporate the tests and the documentation into the Boost framework. Guidance here is welcome. - Anything else that I may have overlooked. Thanks for your input. I hope this library is close to Boost standards and can be improved to the point of being a worthwhile inclusion within the set of libraries. -- Brook Milligan Internet: brook(a)nmsu.edu Department of Biology New Mexico State University Telephone: (505) 646-7980 Las Cruces, New Mexico 88003 U.S.A. FAX: (505) 646-5665

4 4

Re: [boost] Build/install problems: BOOST 1_34 using VS.net
by Thomas Witt 07 May '07

07 May '07

1 0

Re: [boost] Build/install problems: BOOST 1_34 using VS.net
by David Abrahams 07 May '07

07 May '07

on Mon Apr 30 2007, Kirit Sælensminde <kirit.saelensminde-AT-gmail.com> wrote: > I'm going to (re-)use this thread as I'm building Boost 1.34.0 with MSVC > .NET 2003 (7.1 SP1) as well. > > I'm building with the same copy of BJAM as I used to build 1.33.1 with. > I've created a user-config.jam file containing a single line: > using msvc : 7.1 ; > > I'm doing the build from the MSVC .NET command prompt which I think > should have all of the compiler's settings already. The build command > I'm using is: > > E:\FOST.3\external\boost_1_34_0>bjam --toolset=msvc > --prefix=.\install\basic "-sBUILD=debug release <runtime-link>dynamic > <threading>multi" install Please read the new getting started guide. you're using options (-sBUILD=...) that are no longer supported. Your build command should be something like: bjam --toolset=msvc -prefix=.\install\basic debug release runtime-link=dynamic threading=multi of course, from the top level, both debug and release are built by default, so bjam --toolset=msvc -prefix=.\install\basic runtime-link=dynamic threading=multi should be sufficient. > I seem to be getting a lot of warnings and a couple of errors, but > they're not hanging around for long enough to capture. bjam ... arguments > buildlog.txt 2>&1 > I can try to > capture them if anybody wants to see what they are. > > In the install directory in this path: > E:\FOST.3\external\boost_1_34_0\install\basic\include\boost-1_34\boost\compatibility\cpp_c_headers > > I get a .svn directory which shouldn't be there. I seem to remember this > happening with 1.33.1 as well but don't know for sure now. Hmm, this looks like a problem for our release manager. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com

1 0

[1.34.0] make check fails on Linux
by Thomas Witt 07 May '07

07 May '07

Begin forwarded message: > From: "Tarjei Knapstad" <tarjei.knapstad(a)gmail.com> > Date: April 26, 2007 8:16:14 AM PDT > To: "Thomas Witt" <witt(a)acm.org> > Subject: Re: [boost] [1.34.0] Volunteers needed to check tarballs > > On 4/26/07, Thomas Witt <witt(a)acm.org> wrote: >> >> On Apr 26, 2007, at 6:55 AM, Tarjei Knapstad wrote: >> >> > >> > Thanks, I've downloaded and started a build. Will check that it >> > builds, that the tests work, examples work, docs are OK and >> anything >> > else I can think of and get back to you as soon as possible. (I'm >> > doing this on a Core 2 Duo laptop running CentOS 4.4 btw). >> > >> > > My experiences so far... :) > <snip/> > > ==== Unit tests ==== > > 'make check' fails: > > user-config.jam: No such file or directory > warning: No toolsets are configured. > warning: Configuring default toolset "gcc". > warning: If the default is wrong, you may not be able to build C++ > programs. > warning: Use the "--toolset=xxxxx" option to override our guess. > warning: For more configuration options, please consult > warning: http://boost.org/boost-build2/doc/html/bbv2/advanced/ > configuration.html > notice: could not find main target test > notice: assuming it's a name of file to create > don't know how to make <e>test > ...found 1 target... > ...can't find 1 target... > > If I manually copy boost_1_34_0/user-config.jam to the status/ > directory it can find the toolset and the warnings disappear, but it > still doesn't find any targets. > > Am I supposed to build and run the tests some other way? (I couldn't > find any docs) > > <snip/> > > Except for not being able to run the unit tests it looks good to me. > > Regards, > -- > Tarjei -- Thomas Witt witt(a)acm.org

2 1

Re: [boost] Boost 1.34.0 Beta released
by David Abrahams 07 May '07

07 May '07

on Mon May 07 2007, Scott Meyers <usenet-AT-aristeia.com> wrote: > I'm confused. There are 69 libraries listed at > http://boost.org/libs/libraries.htm#Alphabetically. The announcement says that > 1.34 beta adds 5 new libraries (Foreach, statechart, TR1, Typeof, and > Xpressive), for a total of 74. But I see only 64 libraries listed at > http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… > , and that latter list does not include all the libraries listed for 1.33. I can't speak to that part. > I'm also confused about the contents of 1.34 versus what's been accepted at > Boost since 1.33. "Latest News" at Boost lists the following libraries as > having been accepted since the beginning of 2006: > - April 11, 2007 - Quantitative Units Accepted > - April 2, 2007 - Intrusive Containers Accepted > - March 3, 2007 - Bimap Accepted > - February 19, 2007 - Accumulators Accepted > - November 28, 2006 - Function Types Accepted > - November 7, 2006 - Generic Image Library Accepted > - September 21, 2006 - Message Passing Accepted > - June 6, 2006 - Fusion Library Accepted > - May 20, 2006 - Property Tree Accepted > - April 12, 2006 - Promotion Traits Accepted > - March 22, 2006 - Asynchronous I/O Library Accepted > - February 17, 2006 - Shared Memory Library Accepted > But most of these libraries are not listed at > http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… > . > > Maybe I'm just not looking in the right place for a comprehensive listing of the > contents of 1.34. > > Can somebody please clarify the situation regarding the contents of 1.34? 1.34 had a "new code" freeze long ago (maybe a year or more!) but we kept accepting libraries. The libraries accepted since then will go into 1.35, which we hope to release very soon after 1.34. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com

1 0

Re: [boost] [review] Boost.Guid
by Peter Dimov 07 May '07

07 May '07

Peter Dimov wrote: > For the default seed, you might want to look into combining several > sources of entropy (unpredictable values) such as > > - time(0) > - clock() > - the values of an unsigned char[] array that is allocated on the > stack and not initialized > - the addresses of some variables or functions > - the address of a newly allocated object > - anything else that you can come up with Here's one implementation of this. Feel free to use it: #include "sha1.hpp" #include <cstdlib> #include <ctime> #include <cstring> #include <cstdio> #include <memory> namespace boost { namespace detail { inline unsigned * sha1_random_digest_state() { static unsigned state[ 5 ]; return state; } inline void sha1_random_digest( unsigned (&rd) [ 5 ] ) { SHA1 sha; unsigned * ps = sha1_random_digest_state(); unsigned state[ 5 ]; std::memcpy( state, ps, sizeof( state ) ); // harmless data race sha.Input( (unsigned char const*)state, sizeof( state ) ); sha.Input( (unsigned char const*)&ps, sizeof( ps ) ); { std::time_t tm = std::time( 0 ); sha.Input( (unsigned char const*)&tm, sizeof( tm ) ); } { std::clock_t ck = std::clock(); sha.Input( (unsigned char const*)&ck, sizeof( ck ) ); } { unsigned rn[] = { std::rand(), std::rand(), std::rand() }; sha.Input( (unsigned char const*)rn, sizeof( rn ) ); } { unsigned char buffer[ 20 ]; if( std::FILE * f = std::fopen( "/dev/urandom", "rb" ) ) { std::fread( buffer, 1, 20, f ); std::fclose( f ); } // using an uninitialized buffer[] if fopen fails // intentional, we rely on its contents being random sha.Input( buffer, sizeof( buffer ) ); } { unsigned * p = new unsigned; sha.Input( (unsigned char const*)p, sizeof( *p ) ); sha.Input( (unsigned char const*)&p, sizeof( p ) ); delete p; } sha.Input( (unsigned char const*)rd, sizeof( rd ) ); unsigned digest[ 5 ]; sha.Result( digest ); for( int i = 0; i < 5; ++i ) { // harmless data race ps[ i ] ^= digest[ i ]; rd[ i ] ^= digest[ i ]; } } } // namespace detail } // namespace boost #include <iostream> #include <iomanip> static void print_digest( unsigned const (&digest) [ 5 ] ) { std::cout << std::hex << std::setfill('0') << std::uppercase << std::setw( 8 ) << digest[ 0 ]; for( int i = 1; i < 5; ++i ) { std::cout << '-' << std::setw( 8 ) << digest[ i ]; } std::cout << std::endl; } int main() { unsigned rd[ 5 ]; for( int i = 0; i < 4; ++i ) { boost::detail::sha1_random_digest( rd ); print_digest( rd ); } }

2 1