- Boost-users - lists.preview.boost.org

Building boost 1.33.1 with Comeau 4.3.3
by Pooyan McSporran 02 Jan '06

02 Jan '06

I'm having problems trying to build boost 1.33.1 with comeau 4.3.3 on Linux. Firstly, I verified that the como compiler is working by creating a 'hello world' test program, and building it with the como compiler and running it. I tried to build Boost using the information at http://www.boost.org/tools/build/v1/como-tools.html For example, $ tar -xjf boost_1_33_1.tar.bz2 $ cd boost_1_33_1 $ bjam -sTOOLS=como -sCOMO_PATH=/cc -sCOMO_INCLUDE_PATH=/cc/lib -sCOMO_STDLIB_PATH=/cc stage This results in numerous errors: Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). **** wide char i/o not supported by libcomo standard library **** **** skipping build of <@boost!libs!serialization!build>libboost_wserialization.a; toolset= como variant= debug **** **** wide char i/o not supported by libcomo standard library **** **** skipping build of <@boost!libs!serialization!build>libboost_wserialization.a; toolset= como variant= release **** **** DLLs cannot be built with this compiler **** **** skipping build of <@boost!libs!serialization!build>libboost_serialization.so; toolset= como variant= debug **** **** DLLs cannot be built with this compiler **** **** skipping build of <@boost!libs!serialization!build>libboost_serialization.so; toolset= como variant= release **** **** wide char i/o not supported by libcomo standard library **** **** DLLs cannot be built with this compiler **** **** skipping build of <@boost!libs!serialization!build>libboost_wserialization.so; toolset= como variant= debug **** **** wide char i/o not supported by libcomo standard library **** **** DLLs cannot be built with this compiler **** **** skipping build of <@boost!libs!serialization!build>libboost_wserialization.so; toolset= como variant= release **** ...patience... ...patience... ...patience... ...found 6796 targets... ...updating 789 targets... MkDir1 stage MkDir1 stage/lib MkDir1 bin MkDir1 bin/boost MkDir1 bin/boost/libs MkDir1 bin/boost/libs/regex MkDir1 bin/boost/libs/regex/build MkDir1 bin/boost/libs/regex/build/libboost_regex.so MkDir1 bin/boost/libs/regex/build/libboost_regex.so/como MkDir1 bin/boost/libs/regex/build/libboost_regex.so/como/debug como-C++-action bin/boost/libs/regex/build/libboost_regex.so/como/debug/c_regex_traits.o Comeau C/C++ 4.3.3 (Oct 24 2003 16:00:23) for RedHat_LINUX_INTEL_ELF Copyright 1988-2003 Comeau Computing. All rights reserved. MODE:strict errors C++ "/cc/lib/stl_tempbuf.h", line 53: error: identifier "INT_MAX" is undefined if (__len > ptrdiff_t(INT_MAX / sizeof(_Tp))) ^ "/cc/lib/stl_tempbuf.h", line 101: error: identifier "INT_MAX" is undefined if (_M_len > (ptrdiff_t)(INT_MAX / sizeof(_Tp))) ^ "/cc/lib/limits", line 205: error: identifier "CHAR_BIT" is undefined __STL_DECLARE_LIMITS_MEMBER(int, ^ (etc!) Am I doing something stupid? For what it's worth, I've been using boost with gcc for quite some time now with no problems, but decided to give it a try with comeau, but no luck yet. I have searched online for solutions to this, but couldn't find any solutions that work for me.

2 2

How to identify Boost libraries which support eVC++ compiler
by Mateusz Łoskot 01 Jan '06

01 Jan '06

Hi, I'm trying to use Boost libraries with eMbedded Visual C++ 4.0 compiler (Windows CE applications development). I'd like to catalogue as much as possible Boost libraries which can be used with eVC++ 4.0 compiler. Currently, I can use smart pointers successfully. I also tried to use boost\date_time libraries and I found most of them can not be used with eVC++. I got "unknown CE compiler" error message. So, I suppose I will get that message in most cases. As I revealed there is a compiler detection mechanism in file boost\config\compiler\visualc.hpp but I couldn't find out how exactly it is used. I'd like to identify all Boost libraries which can not be used with eVC++. Could anyone give me a few hints about how to start such identification? Are there any macro definitions or can I expect that visualc.hpp can help me in this task? Thank in advance for all comments Best regards -- Mateusz Łoskot http://mateusz.loskot.net

3 11

Problems with CVS
by Mateusz Łoskot 01 Jan '06

01 Jan '06

Hi, Yesterday I met some problems with accessing Boost CVS. I started to checkout the CVS HEAD using anonymous user. The process was going well but after a few minutes I got many timeouts errors. I tried to checkout again and update my existing sandbox but without any success. Here are errors I got when using command line CVS client: D:\__projects_mloskot\boost>cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost login Logging in to :pserver:anonymous@cvs.sourceforge.net:2401:/cvsroot/boost CVS Password: cvs [login aborted]: Error reading from server cvs.sourceforge.net: 0: No such file or directory D:\__projects_mloskot\boost>cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost co -P boost cvs [checkout aborted]: Error reading from server cvs.sourceforge.net: 0: Invalid argument D:\__projects_mloskot\boost>cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost update -P boost cvs [update aborted]: Error reading from server cvs.sourceforge.net: 0: Invalid argument As I checked CVS Web Browser is working well, so CVS on SF.net seems to be up. Am I doing something wrong? Cheers -- Mateusz Łoskot http://mateusz.loskot.net

1 1

Re: [Boost-users] [multi_index] const_mem_fun with an inherited member function
by JOAQUIN LOPEZ MU?Z 01 Jan '06

01 Jan '06

----- Mensaje original ----- De: Matt Steele <steelerm(a)netlab.uky.edu> Fecha: Domingo, Enero 1, 2006 8:32 pm Asunto: Re: [Boost-users] [multi_index] const_mem_fun with an inherited member function [...] > Your suggestion worked without any changes (runtime tested it > with a few toy calls to insert()/find() ). However, if instead of > invoking the global get<>() function template, I try to call the > member function template, > > return t.get<N>(); > > I get this compile error: > > error: invalid use of member (did you forget the '&' ?) > > Do you know if this code should compile? If not, is there a way > to call > a member function template in this context without relying on a global > function wrapper? Try return t.template get<N>(); Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

Re: [Boost-users] [multi_index] const_mem_fun with an inherited member function
by Matt Steele 01 Jan '06

01 Jan '06

Hello Joaquin, Thank you for your response. > 2. I think that the code won't work as expected: const_mem_fun > has some overloads of operator() in order to support > chained pointers (http://tinyurl.com/9cd2v) that will hide > the implicit conversion from const tuple<int>& to > const tuple<int>::inherited&. Could you please try to insert > some element in my_tuple_container_type? My hunch is that > you'll get a compiler error about tuple<int> not having > operator*. Please report back. You're right; the code fails to compile and for the reason you give. > remains. My suggestion is that you simply provide a user-defined > key extractor like this (uncompiled, beware typos): > template<typename Tuple,int N> > struct tuple_member_extractor > { > typedef typename > boost::tuples::element<N,Tuple>::type result_type; > > const result_type& operator()(const Tuple& t)const > { > return boost::tuples::get<N>(t); > } > }; > > Hope this helps; I'd appreciate if you reported on the > success/failure of this approach. > Your suggestion worked without any changes (runtime tested it with a few toy calls to insert()/find() ). However, if instead of invoking the global get<>() function template, I try to call the member function template, return t.get<N>(); I get this compile error: error: invalid use of member (did you forget the '&' ?) Do you know if this code should compile? If not, is there a way to call a member function template in this context without relying on a global function wrapper? Thanks, Matt

1 0

Re: [Boost-users] Why is boost::thread::mutex noncopyable?
by Phil Endecott 01 Jan '06

01 Jan '06

>>Can someone help me to understand why boost::thread::mutex is >>noncopyable? I expect that there is a good reason, but I can't see it >>at the moment. > > http://www.boost.org/doc/html/threads/faq.html#id2786688 Thanks for the link. Here is the text: Why do Mutexes have noncopyable semantics? To ensure that deadlocks don't occur. The only logical form of copy would be to use some sort of shallow copy semantics in which multiple mutex objects could refer to the same mutex state. This means that if ObjA has a mutex object as part of its state and ObjB is copy constructed from it, then when ObjB::foo() locks the mutex it has effectively locked ObjA as well. This behavior can result in deadlock. Other copy semantics result in similar problems (if you think you can prove this to be wrong then supply us with an alternative and we'll reconsider). I disagree with the first comment: "The only logical form of copy would be to use some sort of shallow copy semantics in which multiple mutex objects could refer to the same mutex state." What's wrong with the copy of a mutex being a new independent mutex? (There's a problem if you copy a locked mutex, but I don't propose to do that.) --Phil.

3 2

Re: [Boost-users] Why is boost::thread::mutex noncopyable?
by Phil Endecott 01 Jan '06

01 Jan '06

>>Can someone help me to understand why boost::thread::mutex is >>noncopyable? I expect that there is a good reason, but I can't see it >>at the moment. > > http://www.boost.org/doc/html/threads/faq.html#id2786688 I'm being a bit dense - a subsequent FAQ shows how you can write a copy-constructor for a struct that contains a mutex that explicitly copies the data, giving you a new default-constructed mutex. The constructor can even lock the thing it is copying. --Phil.

1 0

Why is boost::thread::mutex noncopyable?
by Phil Endecott 31 Dec '05

31 Dec '05

Dear All, Can someone help me to understand why boost::thread::mutex is noncopyable? I expect that there is a good reason, but I can't see it at the moment. In my multithreaded application I have a struct with some uninteresting data in it, but I want updates to the struct as a whole to be atomic so I have a mutex. For example: struct person { string firstname; string surname; mutex m; }; I want to be able to put these structs in a container. Say a map: map<int,person> people; person p; people.insert(make_pair(1,p)); But I can't do this because the mutex is noncopyable and inserting copies it. Yes, I could have a map<int,person*>. But I don't understand why I'm forced to do that. Of course, copying a struct person while the mutex is locked would be a bad thing to do. And copying the struct is not thread safe. But higher-level constraints can prevent this sort of thing from happening; for example, I might create my map while only one thread exists. Can anyone offer any insight? Thanks, --Phil.

2 1

Re: [Boost-users] [multi_index] const_mem_fun with an inherited memberfunction
by JOAQUIN LOPEZ MU?Z 31 Dec '05

31 Dec '05

Hello Matt, ----- Mensaje original ----- De: Matt Steele <steelerm(a)netlab.uky.edu> Fecha: Sábado, Diciembre 31, 2005 8:21 am Asunto: [Boost-users] [multi_index] const_mem_fun with an inherited memberfunction > I am trying to use Boost.Multi-index (version 1.33.0) to store a > set of > boost::tuples, and it appears that const_mem_fun has some difficulties > when the desired member function is inherited from a base class. The > following typedef > > typedef multi_index_container< > tuple<int>, > indexed_by< ordered_non_unique< const_mem_fun< tuple<int>, > const int&, > &tuple<int>::get<0> > > > > > > > > my_tuple_container_type; > > yields this error (edited for clarity) on my compiler (g++ 4.0.3): > > &TupleBaseClass<int>::get' is not a valid template argument for > type > 'const int& (tuple<int>::*)()const' because it is of type > 'const int& (TupleBaseClass<int>::*)const' > note: standard conversions are not allowed in this context > > > Now the declaration of boost::tuple has something like this: > > template <class T> > class tuple : public TupleBaseClass<T> { > public: > typedef typename TupleBaseClass<T> inherited; > ... > }; > > (Also, as far as I can tell, get<0>() is declared and implemented in > TupleBaseClass, not tuple). The public typedef 'inherited' looked > promising, so I modified my code as follows: > > typedef multi_index_container< > tuple<int>, > indexed_by< ordered_non_unique< const_mem_fun< > tuple<int>::inherited, > const int&, > &tuple<int>::get<0> > > > > > > > > my_tuple_container_type; > > and that compiles. > > I have a few questions/comments about all this. First of all, is my > compiler correct to generate the error for the first case? Unfortunately, it is correct. There are some quirks about the contravariance rules of pointer to members in C++. For instance, the following is legal (as expected): struct A { int x; }; struct B:A{}; int main() { int B::* p=&B::x; } whereas the following is not: struct A { int x; }; struct B:A{}; template<int B::*Ptr> struct foo{}; int main() { // error: argument of type "int A::*" is incompatible with // template parameter of type "int B::*" foo<&B::x> f; } To me, this is a defect in the standard, but there might be a reason for this behavior. I'll go ask in comp.std.c++. > Secondly, is > the above workaround satisfactory? My opinion is that it's a little > ungainly; it appears to me that boost::tuple is a derived type for > implementation reasons, and I'd rather not have to know about that > fact. It is unsatisfactory for two reasons: 1. As you say, having to expose an implementation artifact is ugly. 2. I think that the code won't work as expected: const_mem_fun has some overloads of operator() in order to support chained pointers (http://tinyurl.com/9cd2v) that will hide the implicit conversion from const tuple<int>& to const tuple<int>::inherited&. Could you please try to insert some element in my_tuple_container_type? My hunch is that you'll get a compiler error about tuple<int> not having operator*. Please report back. As for issue #2, I've corrected the problem (for SFINAE-capable compilers) for the next Boost 1.34 release. Even so, issue #1 remains. My suggestion is that you simply provide a user-defined key extractor like this (uncompiled, beware typos): template<typename Tuple,int N> struct tuple_member_extractor { typedef typename boost::tuples::element<N,Tuple>::type result_type; const result_type& operator()(const Tuple& t)const { return boost::tuples::get<N>(t); } }; Hope this helps; I'd appreciate if you reported on the success/failure of this approach. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

Re: [Boost-users] multi_index new user question
by JOAQUIN LOPEZ MU?Z 31 Dec '05

31 Dec '05

Hello Evan, ----- Mensaje original ----- De: Evan Carew <carew(a)pobox.com> [...] > int main(){ > const people_set::nth_index<2>::type& resstreet_index=ps.get<2>(); > pair<people_set::iterator, people_set::iterator> range; > range = resstreet_index.equal_range((*domoItor).first); > } > > The above code doesn't compile. > > - ---Fourth entry: > By changing the pair instance to: > > pair<people_set::nth_index<2>::type::iterator, > people_set::nth_index<2>::type::iterator> range; > > I finally got it to compile. I managed this not by reading the > tutorialfor the library (the information isn't there) Well, you're right there's no explicit mention to this issue in the tutorial. The info can be extracted from the reference, though. In any case, I'll try to improve the docs on this and add some comments on how to obtain index iterators. Thanks for the feedback! > but from > reading the > rather prodigious code in multi_index. Wow, this is quite an achievement. The code can look very unintelligible. > > - ---Fifth entry: > Am I headed in the right direction, or is there specific interface > that > defines the iterator types in a less painful/safe way? > You've used one of several syntaxes for getting the type of the index #2 iterator. Other possibilities are: people_set::index<resstreetnum>::type::iterator people_set::nth_index_iterator<2>::type people_set::index_iterator<resstreetnum>::type nth_index<people_set,2>::type::iterator index<people_set,resstreetnum>::type::iterator nth_index_iterator<people_set,2>::type index_iterator<people_set,resstreetnum>::type Since you've assigned tags to your indices, it is probably nicer to use some of the tag variations instead of those based on the index ordinal. Other than this, no syntax is particularly clearer or more concise. You may also want to follow Todd Day's suggestion in another reply to your post, and use some typedef's in order to increase code readability. For instance, if you define typedef people_set::index<resstreetnum>::type resstreet_index_type; then the iterator you're looking for is simply resstreet_index_type::iterator which looks quite obvious, since it follows exactly the same pattern as you'd adopt for an STL container. HTH Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0