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

regex problems
by Paul Scruby 18 Nov '03

18 Nov '03

The boost::regex class is crashing when I construct it with some regular expressions. For example: "(value|default)[^}]*\{" will crash and "value|default" does not. Is this a bug, or am I doing something wrong? I am running gcc2.96 and boost1.30.2. I have attached an example src including Makefile. Thanks in advance, Paul

3 3

Newbie question, linking problems
by Mrk 17 Nov '03

17 Nov '03

Hello, I'm trying to get regexp to work under vc6, STL 4.5.3 and boost 1.30.2 but sadly I'm running into some problems. Did anyone ever had this problem with the following methods ? error LNK2001: unresolved external symbol "public: static void __cdecl boost::w32_regex_traits<char>::transform_primary( ... error LNK2001: unresolved external symbol "public: static void __cdecl boost::w32_regex_traits<char>::transform( ... Thanks, Mrk

1 0

Re: [Boost-users] [BGL] Problem with color maps for undirected_dfs_visit
by Jeremy Siek 17 Nov '03

17 Nov '03

Hi Tarjei, On Friday, November 14, 2003, at 05:33 AM, Tarjei Knapstad wrote: > On Thu, 2003-11-13 at 17:09, Jeremy Siek wrote: >> Hi Tarjei, >> >> You need to initialize the edge index property map (only the vertex >> index >> map is automatically initialized, and then only for VertexList=vecS). >> > > Hmm, ok, but I still don't quite understand. I thought that > initializing > the std::vector holding the colors was sufficient...? To my > understanding an iterator_property_map is just a property map which > iterates through some other container (that can provide a > RandomAccessIterator) actually holding the properties? Yes, your edge color map is initialized just fine, but you also need to initialize the edge index map. Here's the reason why: your edge color map uses the edge index map to go from an edge descriptor to an integer offset, which is then used to access into the color vector. Currently, your edge index map is initialized to random garbage, so you are going out-of-bounds when accessing the edge color vector. See the example file exterior_properties.cpp, BTW, you don't need to declare an edge_color property for the adjacency_list because you are using an external edge color map. > > Obviously there's some connection I don't quite get here... I also > don't > quite understand the EColorValue uv_color = get(edge_color, *ei); call > in undir_dfv_impl. It asks for the edge_color at the edge_descriptor > *ei, but from where? > > Anyway, I don't really even need an edge_index property here (or do > I?), > it was more or less to try to get this working. Yes, you need it for the reason given above. BTW, if you switch to using an internal edge color property, then you won't need the edge index property, or the edge color vector. Cheers, Jeremy

2 1

GRAPHVIZ_DIRECTED macro definition?
by Soumitra Chatterjee 17 Nov '03

17 Nov '03

Hi, In the file .../libs/graph/src/graphviz_parser.y we have the following: #ifndef GRAPHVIZ_DIRECTED #error Need to define the GRAPHVIZ_DIRECTED macro to either 0 or 1 #endif I couldn't locate the definition for the above macro in my boost installation. Do we need to define it explicitly, or am I missing some file(s)? Thanks, Soumitra

2 1

Error 112: Missing directory LEDA
by Soumitra Chatterjee 17 Nov '03

17 Nov '03

Hi, I have downloaded boost-1.30.2, and while trying to compile/test it, I am getting the error(s): Error 112: "/TESTC++/Boost-1.30.2/boost/graph/leda_graph.hpp", line 33 # Include file <LEDA/graph.h> not found. #include <LEDA/graph.h> ^^^^^^^^^^^^^^ [...snip...] The directory 'LEDA' seems to be missing from the downloaded package. Have I missed something during the install process, or is there something else to be done after unpacking the installation package? I am using JAM for the build. Thanks, Soumitra

3 2

Re: Intoductory Boost Presentation
by Jorg Brown 16 Nov '03

16 Nov '03

Matt - The corrected code is indeed much better. May I suggest using std::vector instead of vector? The typedef of FooPtr is fine, it turns out; it's the typedef of struct Foo that was the problem. I had declared Foo within main as well, and that blocks the use of boost::shared_ptr on it. As long as Foo is declared at global scope, all is well. As for the correct output, my compiler gives me 3, then 2, then 1. I talked it over with a friend, and I guess the order of the 2 vs 1 is undefined, and depends on your STL's implementation of std::vector. As for the crazy aunt in the basement, the comment was meant for an internal list that only 20-30 people are on, not meant for general consumption, and probably merits an extra thread by itself. Put simply, using boost can generate a surprising amount of code and overhead. This is true of STL as well. There are even some good books describing STL; I happen to like Plauger/Stepanov/Lee/Musser, as well as Jasoutis. But nowhere do I see any reference as to what the downsides are - and nowhere do I see any concise explanation of why an enormous amount of code (660 bytes in an optimized, no-symbols build) is generated when I say something as simple as void Testbed(void) { boost::function<void> SimpleFPtr(&Testbed); } When you say "I was trying to generate interest in these libraries and thus didn't want to focus too much on the negatives", I can understand your point of view, but what I see in real life is that people start using boost::function everywhere they used to use plain old function pointers, with nary a clue that their code size just exploded with no benefit. But like I said, it's worth a whole other thread. Thanks for fixing the code and responding so quickly! jorg -----Original Message----- From: "Matt S Trentini" <matt_s_trentini(a)hotmail.com> Reply-To: Boost Users mailing list <boost-users(a)lists.boost.org> Date: Tue, 11 Nov 2003 23:19:12 +1100 To: boost-users(a)lists.boost.org Subject: [Boost-users] Re: Intoductory Boost Presentation Heya Jon, Ah, the smart_ptr example, I knew that would come back to bite me! ;) I changed this example at the last minute in an effort to simplify but, as your co-worker correctly points out, there are many errors in it. The correct code is below though the graphic requires change (yes, I could have change the list.push_front() to a push_back but I like to see the variety!). int main() { typedef boost::shared_ptr<Foo> FooPtr; vector<FooPtr> foo_vector; list<FooPtr> foo_list; FooPtr foo_ptr( new Foo(1) ); foo_vector.push_back( foo_ptr ); foo_list .push_back( foo_ptr ); foo_vector.push_back ( FooPtr( new Foo(2) ) ); foo_list .push_front( FooPtr( new Foo(3) ) ); } You'll notice that I left the typedef in there. I can't find anything in the standard (or with google) about it being illegal in main, nor does my compiler emit any warnings. Can anyone shed some light on this? And I've got to disagree with your friend about the correct ordering - the expected output is 3, 1, 2 (Remember that foo_ptr gets deleted first). I'll endeavour to fix this example up and upload the changes over the next couple of days. As for these comments: > > The rest of the pages have the classic boost downfall: they > > don't discuss any of the pitfalls, performance problems, or > > code bloat issues, which frankly, seem like the "crazy aunt > > in the basement" of boost. I'll defend myself on two fronts. First, it's an introductory presentation - I was trying to generate interest in these libraries and thus didn't want to focus too much on the negatives. Secondly, I _did_ cover some of those points - like all good presentations not everything is contained in the bullet points. Thanks for the feedback though, it's helping to make this presentation better! Cheers, Matt PS If there are any other problems that you or your co-worker have found please don't hesitate to report them! _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users ------ End of Forwarded Message

3 2

Intoductory Boost Presentation
by Matthew S Trentini 16 Nov '03

16 Nov '03

Heya Everyone, I recently gave a presentation to my work colleagues on the wonders of the Boost library. Many weren't aware of what it was or what it could do so it just contains an overview and some coverage on nine of the libraries (with short code examples). It went for nearly an hour and was pretty well received, so I thought that maybe someone else out there could use the material. Please feel free to download (it's in a variety of formats) from here: http://www.alphalink.com.au/~mattyt/BoostPresentation1/boost.html Cheers, Matt PS If you want to modify/publish/whatever that's fine... _________________________________________________________________ Hot chart ringtones and polyphonics. Go to http://ninemsn.com.au/mobilemania/default.asp

7 10

Re: [Boost-users] Building Regex++ lib on Pocket PC using EmbeddedVC++4.0
by Reuti＠sdc.canon.co.in 16 Nov '03

16 Nov '03

Thanx. With latest version I could build but I could not create import library corressponding to dll created. Is there some macro for this? ===== Reuti "John Maddock" <john(a)johnmaddock.co.uk> To: "Boost Users mailing list" <boost-users(a)lists.boost.org> Sent by: cc: boost-users-bounces@list Subject: Re: [Boost-users] Building Regex++ lib on Pocket PC s.boost.org using EmbeddedVC++4.0 11/13/2003 05:32 PM Please respond to Boost Users mailing list > Has anyone tried building regex++ lib for PPC using EVC++? I've never tried with that compiler - I think it's even worse than VC6 for conformance? > I can build it using VC++6.0 using the .mak files supplied with it.But I am > getting errors and warnings. > Error is regarding the use of typename keyword in lib source and warning is > about C++ Exceptions unwinding capability. Defining BOOST_NO_EXCEPTIONS should fix that - in fact it should get automatically set for vc with no eh support, so there could be a config bug there. > I replaced C++ try, catch by Win32 __try , __except but don't know what to > do with template error? What is there error: you may be able to just remove the typename keyword to fix the problem? John. _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 1

Preprocessor Metaprogramming Problem
by Mitch 16 Nov '03

16 Nov '03

I'm trying to figure out the longest sequence in a sequence. Here's the MACRO I tried. #define OP(size, state, elem) BOOST_PP_MAX(state, BOOST_PP_SEQ_SIZE(elem)) #define MACRO(seq) BOOST_PP_SEQ_FOLD_LEFT(OP, 0, seq) If I process ((a)(b))((c)) I get 2 back as expected. However, the extra parenthesis seems awkward. I'd like to process ((a)(b))(c) instead, but can't. The '(c)' gets coverted to plain 'c' as the elem parameter to OP and that's not a valid sequence. Any ideas? Mitch

1 0

boost::shared_ptr performance
by Matthew Wilson 15 Nov '03

15 Nov '03

[I posted this in boost.devel, but got no response. Presumably that was the wrong group. :)] Hi Boosters I'm just doing some research on reference-counting, and contrasting self-counting types with externally counted types, the latter effected with the rather excellent shared pointer technique. [As a side question, is it true that Nicolai Josuttis was the inventor of the technique?] Naturally, one of the shared pointer's I've used is boost::shared_ptr. The measurements have demonstrated some surprising performance characteristics for shared_ptr in particular, and I want to solicit the opinion of the expert's here before I make any bold claims, as some results are just too surprising for me to trust them. There are five types tested. 1. A self-counting type, using an ancient Synesis (my company) template ref-counting bolt-in class 2. A self-counting type, using a custom-written (for this test) template ref-counting bolt-in class 3. Externally counting, using boost::shared_ptr 4. Externally counting, using a custom-written (for this test) shared pointer type 5. Externally counting, using a custom-written (for this test) shared pointer type, which has a custom allocator for the shared count members There were three scenarios investigated, and the same algorithms were applied to the above five types A: Saving refs vector<smart-ptr> ptrs; loop (100,000 times) { smart-ptr sp1(new Thing); sp1 = sp1; smart-ptr p2; p2 = p1; smart-ptr p3(p1); smart-ptr p4(p3); smart-ptr p5(p4); smart-ptr p6(p5); process_Thing(p6.get()); // A function to do something (actually it just returns the result of a call on Thing) to prevent elision by optimisation ptrs.push_back(p5); } The whole is executed within a single thread, and the program is tested in both single and multithreaded forms. B: Discarding refs This is identical to A ("Saving refs") except that saving them to the vector of ptrs is omitted. Again, this is done in one thread, and single and multi-threaded forms tested C: Multi-threaded sharing 20 smart-pointers are created, containing 20 Thing instances, in the main thread. Then 20 threads, using the following thread-proc, are created, and executed. Two times are recorded for each scenario: the total time, and the sum of the individual thread-times (obtained by the WinSTL threadtimes_counter, based on the Win32 API function GetThreadTimes()) std::vector<ptr_type> ptrs(ITERATIONS / 10); for(size_t i = 0; i < 10; ++i) { for(size_t j = 0; j < ITERATIONS / 10; ++j) { ptrs.push_back(things[i % things.size()]); } } ITERATIONS is 100,000. things is the shared shared_ptr array The purpose of this one is to really exercise the sharing between threads. Results (all results are expressed in terms of the most costly pointer) ============================================= [Note, all were compiled with Intel 7.0 with very aggressive speed optimisations (-O2 -Ox -QaxMKW /Qvc7 -EHsc), and executed in a single session on an otherwise quiescent 512MB 2GHz XP box.] A (single-threaded) -------------------- 1. Synesis self-counter: 65% 2. Custom self-counter: 58% 3. boost::shared_ptr: 100% 4. custom SharedPtr: 53% 5. custom SharedPtr + rc pool): 48% I was not surprised that the crusty old Synesis type was slower than the custom self-counter. As expected, the custom shared-ptr with rc pool was the fastest. I was a little surprised that the Boost shared_ptr was up to twice as slow. However, they're all within 100% of each other, so it's no big result I guess. A (multi-threaded) -------------------- 1. Synesis self-counter: 90% 2. Custom self-counter: 46% 3. boost::shared_ptr: 100% 4. custom SharedPtr: 28% 5. custom SharedPtr + rc pool): 27% This was surprising. I expected the use of thread-safe operations (atomic increments, etc.) to flatten out the curve, but the reverse has happened. Interestingly, the two real-world types (Synesis::RefCounter and boost::shared_ptr) fair less well. Again, not what I expected. B (single-threaded) -------------------- 1. Synesis self-counter: 65% 2. Custom self-counter: 55% 3. boost::shared_ptr: 100% 4. custom SharedPtr: 59% 5. custom SharedPtr + rc pool): 53% This scenario has a lot more reference-increments, and a lot less deallocation of the reference-counted instance. Nonetheless, the results are virtually identical, in relative terms (the actual times taken are about 50% across the board). B (multi-threaded) -------------------- 1. Synesis self-counter: 71% 2. Custom self-counter: 41% 3. boost::shared_ptr: 100% 4. custom SharedPtr: 32% 5. custom SharedPtr + rc pool): 31% Pretty much the same as with B (single-threaded). The results are the same, in relative terms Up to this point, the results are mildly interesting, but nothing earth shattering. C - (Times are total time, and thread times, respectively) 1. Synesis self-counter: 2.9% 39% 2. Custom self-counter: 2.7% 35% 3. boost::shared_ptr: 100% 100% 4. custom SharedPtr: 1.0% 13% 5. custom SharedPtr + rc pool): 1.2% 15% This scenario tells quite a different tail indeed. One thing to note is that because of the degree of reference-sharing between the ptr-storing vectors in the 20 threads, the ref-count-pool becomes a pessimisation as a result of the number of actual smart pointer instances being created exceeding the arbitrary 1024 cached ref-counts available. It's likely that this number would not be exceeded in real-world scenarios, so the pool is probably still worth having. Naturally, the very big question is: what's happening to boost::shared_ptr? In thread times, it performs 2-3 times worse than in single threaded scenarios (irrespective of whether they are built for single or multiple threads). However, in total time, it performs extremely poorly, up to 100 times slower than some of the others! Clearly, there is some serious contention involved. There are three possibilities I have thought of: (i) It performs very poorly in multi-threaded sharing scenarios. If this is the case, can any people more expert in Boost than me proffer an explanation as to precisely the problem, and is any such person motivated to try and address the issue? (ii) The particular sharing scenario is well away from any real-world scenario in which boost::shared_ptr is likely to be used. If this is the case, why do four different implementations, representing two very different reference-counting strategies, all maintain a consistent relative performance? What are the scenarios for which boost::shared_ptr is optimised? (iii) There are environment settings for which boost::shared_ptr will perform much better. If that's so, can someone help me out with suggestions of what defines to make? Why are these settings not the default. I'd be very interested in your thoughts. Many thanks in advance. -- Matthew Wilson STLSoft moderator (http://www.stlsoft.org) Contributing editor, C/C++ Users Journal (www.synesis.com.au/articles.html#columns) "You can tell a Yorkshireman, but you can't tell him much!" -- Uncle Michael ---------------------------------------------------------------------------- --- _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Property map deletion
by David Ohlemacher 14 Nov '03

14 Nov '03

Hi all. Partway through my app's execution, I find that I no longer need the values in a custom property map (edge). The map potentially may be quite large. What is the best way to empty it? Thanks, -d

3 7

Boost and Windows CE - does it?
by Steve Folly 14 Nov '03

14 Nov '03

Hi, I know the real answer is probably to just 'try it', but I thought I'd ask to see if anyone else has tried this. We have an application framework which makes extensive use of boost, particularly shared pointers. Currently, we can build Win32 and Mac Carbon applications. Has anyone successfully built applications utilising boost for Windows CE? In particular, we've just started looking at the eMbedded Visual C++ 4.0 compiler and the Pocket PC 2003 SDK. -- Regards, Steve.

1 0

Re: 'long long' problem on VC++7.1
by Nick Savoiu 14 Nov '03

14 Nov '03

And here's what's missing.... I'm using the /Za switch (Disable Language Extensions). But I'm a bit puzzled. I would have thought that /Za (a more standard compliant mode) would not fail. Nick "Nick Savoiu" <savoiu(a)ics.uci.edu> wrote in message news:... > That would be a solution but 'long long' appears in quite a few places. So, > I think there's something else that I'm missing... > > Nick > > "Jeff Garland" <jeff(a)crystalclearsoftware.com> wrote in message > news:20031111022332.M81509@crystalclearsoftware.com... > > On Mon, 10 Nov 2003 14:14:04 -0800, Nick Savoiu wrote > > > I'm trying to compile some boost code on VC+7.1 but I get: > > > > > > e:\users\savoiu\Projects\boost-1.30.2\boost\concept_check.hpp(183) : > > > error C2632: 'long' followed by 'long' is illegal > > > > > > Do I need any #defines when using Boost with VC++7.1 or should it > > > work right out of the box? > > > > I believe this is an error in the concept_check code. Try changing the > 'long > > long' to boost::int64_t. > > > > Jeff > >

2 5

Compiler error with STLport-4.6
by Peter Westerstrom 14 Nov '03

14 Nov '03

Hello, I get this internal compiler error below when compiling boost-regex (from cvs today 11 nov 2003) using STLport-4.6. The error do not show up when using STLport-4.5.3 though. Any ideas? Problem in STLport-4.6 or boost, that's the question? cl -Ic:\EON\builds\head\Development\ExternalLibraries\include\stlport /nologo /MT /W3 /GX /O2 /GB /GF /Gy /Ic:\EON\builds\head\Development\ExternalLibraries\include\stlport /I..\..\..\ /D_MT /DWIN32 /DNDEBUG /D_MBCS /D_LIB /c -DBOOST_REGEX_STATIC_LINK -D_STLP_USE_STATIC_LIB -D_RTLDLL -Y- -Fo./vc6-stlport/libboost_regex-vc6-mt-sp-1_31/ -Fdvc6-stlport/libboost_regex-vc6-mt-sp-1_31.pdb ../src/c_regex_traits.cpp Command line warning D4002 : ignoring unknown option '-Y-' c_regex_traits.cpp ..\..\..\boost/detail/allocator.hpp(67) : fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'msc1.cpp', line 1794) Please choose the Technical Support command on the Visual C++ Help menu, or open the Technical Support help file for more information NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop. Peter Westerstrom peterw(a)eonreality.se

3 4

RE: [Boost-users] Building Regex++ lib on Pocket PC using EmbeddedVC++4.0
by Ben Hutchings 14 Nov '03

14 Nov '03

Reuti(a)sdc.canon.co.in <Reuti(a)sdc.canon.co.in> wrote: > Has anyone tried building regex++ lib for PPC using EVC++? > I can build it using VC++6.0 using the .mak files supplied > with it.But I am getting errors and warnings. > Error is regarding the use of typename keyword in lib source > and warning is about C++ Exceptions unwinding capability. > > I replaced C++ try, catch by Win32 __try , __except That isn't going to help you. While the Win32 exceptions will be caught and thrown there will be no unwinding of the stack, i.e. destructors for automatic variables will *not* be called. So the code will not work correctly in case of an exception. The approach I've seen is to call abort() instead of throwing, which is probably not a very good one. > but don't know what to do with template error? > > Can anybody help in this? > Also can it be confirmed that its possible to port it on Win CE? Not with EVC++. I'm afraid it's something of a waste of time to try to compile standard C++ code with it. There has been some work to port GNU C++ to WinCE but it is incomplete and so far as I know only covers SH3 and MIPS whereas the most popular architecture for WinCE now seems to be ARM.

5 5

[BGL] Problem with color maps for undirected_dfs_visit
by Tarjei Knapstad 14 Nov '03

14 Nov '03

I'm trying to implement a DFS visitor and using it with undirected_dfs_visit, but I'm getting a segfault which relates to the edge color map. I've made the following test app for illustration: **************** START CODE **************** #include <vector> #include <boost/graph/adjacency_list.hpp> #include <boost/graph/undirected_dfs.hpp> using namespace boost; struct Types { typedef adjacency_list<vecS, vecS, undirectedS, property<vertex_color_t, default_color_type>, property<edge_color_t, default_color_type, property<edge_index_t, int> > > GraphType; typedef std::vector<default_color_type> ColorVec; typedef color_traits<default_color_type> Color; }; int main() { Types::GraphType g(6); add_edge(0,1,g); add_edge(1,2,g); add_edge(2,3,g); add_edge(2,4,g); add_edge(4,5,g); Types::ColorVec v_colors(num_vertices(g), Types::Color::white()); Types::ColorVec e_colors(num_edges(g), Types::Color::white()); default_dfs_visitor visitor; undirected_depth_first_visit(g, 0, visitor, make_iterator_property_map(&v_colors[0], get(vertex_index, g)), make_iterator_property_map(&e_colors[0], get(edge_index, g))); }; **************** END CODE **************** The code crashes in undirected_dfs.hpp line 73 the first time it's trying to access a color from the edge color map: EColorValue uv_color = get(edge_color, *ei); Valgrind turns up a lot of illegal reads/writes to the edge_color_map as well, so I'm guessing that I've screwed up on the colormap creation. Could anyone point out my error? Also, is this an error that could be caught compile time by adding some sort of concept check? Thanks in advance for any help! Regards, -- Tarjei

2 2

Boost.Thread: inlined constructor in thread_specific_ptr block application start up
by Roland 14 Nov '03

14 Nov '03

Dear Boosters, I am trying to understand how to use the TSS Thread local storage, and came upon a strange behaviour. I do not know if I am doing something wrong here. Maybe someone can help. I am running on Win2K, VC6.0. (GUI Interface programm type) In my main thread I have: struct oops { // inline oops(); // commented out, won't run oops(); // this one starts up ~oops(); private: int i; }; oops::oops() { i = 0; } oops::~oops() { } boost::thread_specific_ptr<oops> value; I am not assigning to value anywhere. Now when I try to start my programm (I tried only the debug version) my GUI never comes up. When I break into with the debugger I can see, that the programm is sitting somewhere in the main message loop (PumpMessage), but never receiving any messages. When not having the inlined version, behaviour is ok. Any help appreciated. Thank you, Roland

1 0

RE: [Boost-users] boost::shared_ptr inside std::list
by Darryl Green 13 Nov '03

13 Nov '03

> -----Original Message----- > From: James Mastro [mailto:jmastro@rochester.rr.com] > Sent: Thursday, 13 November 2003 11:59 AM > To: Boost Users mailing list > Subject: [Boost-users] boost::shared_ptr inside std::list > > > This one has been driving me nuts all day. In a function I have the > following: > > std::list< boost::shared_ptr<MyObject> > * objectList; An uninitialized pointer to a list of shared pointers to MyObject is probably not what you wanted, but its what you defined. I don't think you bug has anything to do with shared pointers... > > > When debugging my code, the debugger (gdb) dies upon entering the > function with this in it. It says "The Debugger has exited > due to signal > 11 (SIGSEGV).The Debugger has exited due to signal 11 > (SIGSEGV)." My dev > tools felt the need to say it twice for some reason. I pulled this out > and put it in a new project all by itself with the same result. > > If I make it not be a pointer, like this: > > std::list< boost::shared_ptr<MyObject> > objectList; > > then there's no problem. Regards Darryl. ########################################################################## This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimise the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. ##########################################################################

2 1

RE: [Boost-users] Re: travelling salesman for BGL ?
by Ben Hutchings 13 Nov '03

13 Nov '03

Dave <better_cs_now(a)yahoo.com> wrote: > You'll be a millionaire (literally!) if you figure out the exact > solution to TSP in an efficient manner! Only if you patent it as a "business method".

1 0

Building Regex++ lib on Pocket PC using Embedded VC++4.0
by Reuti＠sdc.canon.co.in 13 Nov '03

13 Nov '03

Has anyone tried building regex++ lib for PPC using EVC++? I can build it using VC++6.0 using the .mak files supplied with it.But I am getting errors and warnings. Error is regarding the use of typename keyword in lib source and warning is about C++ Exceptions unwinding capability. I replaced C++ try, catch by Win32 __try , __except but don't know what to do with template error? Can anybody help in this? Also can it be confirmed that its possible to port it on Win CE? Thanx in advance. Reuti

2 1

travelling salesman for BGL ?
by Philippe Guglielmetti 13 Nov '03

13 Nov '03

I'm looking for a free "travelling salesman problem" solver. Does anyone know if something exists for the Boost Graph Library ? I found nothing in the book... Is anybody interested in porting existing code, for example http://www.math.princeton.edu/tsp/concorde.html on BGL ? -- Philippe Guglielmetti - www.dynabits.com

3 2

Re: [Boost-users] graph: Min Spanning Tree (advanced start)
by Jeremy Siek 13 Nov '03

13 Nov '03

Hi Matthew, Yes, that is, as long as that initial list of edges forms a tree. Here's my guess as how to do it for prim's minimum spanning tree. You'll have to directly call breadth_first_visit, redoing all the initialization work done in dijkstra and prim (prim calls dijkstra, which then calls bfs). You'll need to initialize the predecessor map to reflect the starting tree, and also you'll want to set the color of the nodes in the starting tree to black. Then you'll have to color the nodes adjacent to nodes in the tree (that aren't in the tree) gray and stick them in the priority queue... that is, all except for one of the nodes adjacent to the tree (pick an arbitrary one). That node will be your starting node for the bfs. In you're using Kruskal's it is a different story... I'll look at that later if you need it. Cheers, Jeremy On Wednesday, November 12, 2003, at 11:24 AM, Matthew Galati wrote: > Is there a way to give an advanced start to solve Min Spanning Tree > using boost/graph? That is, I have a list of edges in my graph that > must be in the Min Spanning Tree (i.e., their cost is -M, for very big > M). > > Since algorithms for MST are greedy, I assume this can be done - but > is their an easy way to interface to boost/graph's MST algorithms? > > Thanks for any help. > Matt > > -- > Matthew Galati > ISE Lehigh University > IBM Service Parts Solutions > 610.758.4042 (Office) > 610.882.0779 (Home) > magh(a)lehigh.edu, magal11(a)us.ibm.com > http://sagan.ie.lehigh.edu/mgalati/ > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

boost::shared_ptr inside std::list
by James Mastro 13 Nov '03

13 Nov '03

This one has been driving me nuts all day. In a function I have the following: std::list< boost::shared_ptr<MyObject> > * objectList; When debugging my code, the debugger (gdb) dies upon entering the function with this in it. It says "The Debugger has exited due to signal 11 (SIGSEGV).The Debugger has exited due to signal 11 (SIGSEGV)." My dev tools felt the need to say it twice for some reason. I pulled this out and put it in a new project all by itself with the same result. If I make it not be a pointer, like this: std::list< boost::shared_ptr<MyObject> > objectList; then there's no problem. Oddly, both versions of the code work fine when run normally (not being debugged.) I don't see what's wrong with the first version. Is it OK to put boost shared ptrs in a std::list? Is there something else I'm missing? Or is my dev environment just having problems? -jim

1 0

Re:[Boost-users] graph: Min Spanning Tree (advanced start)
by rlyon＠comgroup.net.au 12 Nov '03

12 Nov '03

It's no longer necessarily a minimum spanning tree. The exact algorithm will depend upon whether your starting set of edges always is a tree. Regards ... ____________________Reply Separator____________________ Subject: [Boost-users] graph: Min Spanning Tree (advanced start) Author: Matthew Galati <magh(a)lehigh.edu> Date: 12/11/2003 11:24 AM Is there a way to give an advanced start to solve Min Spanning Tree using boost/graph? That is, I have a list of edges in my graph that must be in the Min Spanning Tree (i.e., their cost is -M, for very big M). Since algorithms for MST are greedy, I assume this can be done - but is their an easy way to interface to boost/graph's MST algorithms?

1 0

Re: [Boost-users] int64_t error
by Gilad Suberri 12 Nov '03

12 Nov '03

Thanks. It seems that I do not have the file "stdint.h", so in cstdint.hpp, int64_t is defined in the last #else section (that goes with #ifdef BOOST_HAS_STDINT_H). When operators.hpp is included before this file (cstdint.hpp,) int64_t does not get defined at all because this next statement from cstdint.hpp becomes false: # if defined(BOOST_HAS_LONG_LONG) && \ !defined(BOOST_MSVC) && !defined(__BORLANDC__) && \ (!defined(__GLIBCPP__) || defined(_GLIBCPP_USE_LONG_LONG)) && \ (defined(ULLONG_MAX) || defined(ULONG_LONG_MAX) || defined(ULONGLONG_MAX)) When the include statements are switched around int64_t gets defined. This is connected to posix_time_config.h where "boost/date_time/time_duration.hpp" is included before "boost/date_time/time_resolution_traits.hpp", which causes the above problem. I switched the two include statements and I am not running into that compiler error anymore, but I am not sure if that will cause other compiler errrors. Hope some of this made sense, let me know what you think or if I am missing anything. Thanks. Gilad ----- Original Message ----- From: "Jeff Garland" <jeff(a)crystalclearsoftware.com> To: "Boost Users mailing list" <boost-users(a)lists.boost.org> Sent: Wednesday, November 12, 2003 10:10 AM Subject: Re: [Boost-users] int64_t error > On Wed, 12 Nov 2003 08:42:08 -0500, Gilad Suberri wrote > > Hi, I am compiling my projects on Solaris, using the latest version > > of the boost date_time library. All the gregorian examples compile > > and build fine, but when I try to compile posix_time ones I get this > > error: > > > > ...error details snipped... > > The version of gcc is 3.0.2. > > I do not get this compiler error when I use gcc 2.95.3, but I needed > > to use the newer version. > > > > Any ideas? Thanks. > > I suspect that somehow you are not getting boost::int64_t defined. Although > looking at the logic in boost/config I'm not seeing why at the moment -- you > might experiment with trying to make sure boost::int64_t is defined. I won't > have a chance to look until later as I'm running out the door. Bottom line is > it should work with this compiler... > > Jeff > > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 2

Re: [Boost-users] Re: Intoductory Boost Presentation
by Jon Kalb 12 Nov '03

12 Nov '03

On 11/12/03 12:39 AM, "David Abrahams" <dave(a)boost-consulting.com> wrote: > Jon Kalb <Kalb(a)LibertySoft.com> writes: > >> I will forward this message to him and ask if he wants to comment more >> specifically, but I'll give you one example that he found. I don't recall >> the exact number, but he found that a function call using Boost::function >> generated about 20K of code (in our development environment). I realize that >> in a day when gigabyte hard drives are a dime a dozen it seems miserly to >> worry about 20K, but that is for *one function call*. > > With optimization on? Apparently not. It isn't so bad in the ship build and the hit is not in the invocation, but in the construction. > I find that _very_ hard to swallow, as I have > some idea what's involved under the hood of Boost.Function. Unless, > of course, the size was really going into the function object being > wrapped by Boost.Function... if you're just wrapping (member) > function pointers Boost.Function should generate very little extra > code. Can you have your coworker post an example which demonstrates? He has already posted to this list saying: On 11/11/03 11:25 AM, "Jorg Brown" <jorg(a)microsoft.com> wrote: > an enormous amount of > code (660 bytes in an optimized, no-symbols build) is generated when I > say something as simple as > > void Testbed(void) { > boost::function<void> SimpleFPtr(&Testbed); > } > -- Jon Kalb Kalb(a)LibertySoft.com

1 0

graph: Min Spanning Tree (advanced start)
by Matthew Galati 12 Nov '03

12 Nov '03

Is there a way to give an advanced start to solve Min Spanning Tree using boost/graph? That is, I have a list of edges in my graph that must be in the Min Spanning Tree (i.e., their cost is -M, for very big M). Since algorithms for MST are greedy, I assume this can be done - but is their an easy way to interface to boost/graph's MST algorithms? Thanks for any help. Matt -- Matthew Galati ISE Lehigh University IBM Service Parts Solutions 610.758.4042 (Office) 610.882.0779 (Home) magh(a)lehigh.edu, magal11(a)us.ibm.com http://sagan.ie.lehigh.edu/mgalati/

1 0

RE: [Boost-users] Intoductory Boost Presentation
by Darryl Green 12 Nov '03

12 Nov '03

> -----Original Message----- > From: Jon Kalb [mailto:Kalb@LibertySoft.com] > Sent: Wednesday, 12 November 2003 7:22 AM > To: Boost Users > Subject: Re: [Boost-users] Intoductory Boost Presentation > > > > the documentation (and the code?) deficient? That would be as useful as > > Matt's overview could be to those just getting into/considering using > > boost libs. As it stands, all that the above statement adds is FUD. > > I passed on my friend's comments without attribution because > I didn't ask > his permission and I don't think he really intended the > comments for so > large an audience. His comments were directed to our > co-workers and we know > a little about some of the research that he has done on some > of the Boost > libraries. With that audience it isn't exactly FUD. I agree - FUD is audience dependent. I am 100% serious about thinking that any addition that clarifies what the issues/pitfalls are would be valuable, while FUD definitely isn't. > > I will forward this message to him and ask if he wants to comment more > specifically, but I'll give you one example that he found. I > don't recall > the exact number, but he found that a function call using > Boost::function > generated about 20K of code (in our development environment). > I realize that > in a day when gigabyte hard drives are a dime a dozen it > seems miserly to > worry about 20K, but that is for *one function call*. I don't think he > benchmarked it to see how long it takes to execute this code, > but still I > think he has a point when he talks about code bloat. I'm sure he has a point. I only asked him to make it. I don't really want this to turn into an attack on your co-worker's reasearch - I would honestly like to see some information on these issues. We did some basic tests on the performance of boost::function before using it and found that the actual despatch overhead is very low (which was our main concern at the time) and the size of the actual function wrapper is acceptable. We have not (yet) used boost::function in a context where the allocation performance would be expected to be significant. We didn't specifically check code size, but I can safely say we don't see 20K/function call (and yes, we do care about code size - embedded system). One thing that I have found with boost is that by providing powerful concepts in its libraries it can replace a lot of bloatware libraries/frameworks in a way that reduces overall code size, even though toy benchmarks might indicate otherwise. > > I also think he has a point about discussing the performance > trade-off issue > of each library. When the STL was first introduced, it was so > revolutionary > that it was given a very skeptical reception. But most people > were won over. > The power/overhead ratio was very favorable and it looked > like compilers > would likely improve in ways that would make it even more favorable. Absolutely agreed. Some of the stl tradeoffs don't fit some systems - hence boost:array for example... > > Now we are comfortable with template libraries and are less > skeptical of new > ones. But every library has some overhead cost and has some > applications for > which it is ill-suited. We need to evaluate each library on > its own merits > and never assume that because one was accepted in Boost it > has some magic > property that means there are no performance trade-offs or that the > performance profiles of all Boost libraries are similar. Yes - maybe something like that disclaimer would be a good start in an introductory overview. It is ultimately up to the library user to eveluate these issues - nothing special about boost in that regard. > > Suppose users determine that Boost::function (I'm just > picking on this as an > example) is great for creating flexible interfaces, but > should be avoided > for any inner-loop use or where code size is at a premium. A user would have to determine that from an understanding of what a boost::function really is/does and an understanding of their application of it. In my opinion a statement similar to the above isn't a reasonable way to present usage guidelines for boost::function. If you need a generalised function interface in an inner-loop (hopefully rare) I can't see that boost::function is going to be out-performed significantly by anything else. If you are using a generalised function object interface for invoking functions where the cost of an indirection in the call is a significant part of the cost of the function (and the performance actually matters) you have a design problem. As to code size - there will always be places where code size matters, but I haven't seen a problem - maybe a system where there are a huge number of different boost::function specializations? > That doesn't make > the library worthless, in fact, adding advice about the best > situations to > use the library enhances its value. I agree - I really was asking you/your colleague to provide some information to turn the FUD into something valuable. I don't think boost::function needs any more guidelines, it is pretty well documented. The only one I'd suggest emphasising in an introductory coverage is: Carefully consider whether using boost::ref to avoid copying the target function object is necessary/desirable for performance and/or semantic reasons using boost::function. I just checked, and this is covered in Douglas Gregor's tutorial anyway. Maybe the guideline should just be RTFM..... Regards Darryl Green ########################################################################## This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimise the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. ##########################################################################

1 0

RE: [Boost-users] Re: Intoductory Boost Presentation
by Ben Hutchings 12 Nov '03

12 Nov '03

Matt S Trentini <matt_s_trentini(a)hotmail.com> wrote: <snip> > You'll notice that I left the typedef in there. I can't find > anything in the standard (or with google) about it being illegal in > main, nor does my compiler emit any warnings. Can anyone shed some > light on this? There's nothing wrong with it. A typedef declaration is allowed wherever any other declaration is allowed, except in the condition of a 'for', 'if', 'switch' or 'while' statement. > And I've got to disagree with your friend about the correct ordering > - the expected output is 3, 1, 2 (Remember that foo_ptr gets deleted > first). I don't see any requirement on the order of destruction of sequence elements, so I think it can be either 3, 1, 2 or 3, 2, 1.

2 1

RE: [Boost-users] Intoductory Boost Presentation
by Darryl Green 11 Nov '03

11 Nov '03

Hi Jon, > -----Original Message----- > From: Jon Kalb [mailto:Kalb@LibertySoft.com] > Sent: Tuesday, 11 November 2003 11:16 AM > To: Boost Users > Subject: Re: [Boost-users] Intoductory Boost Presentation > > > On 11/9/03 8:06 PM, "Matthew S Trentini" <matt_s_trentini(a)hotmail.com> > wrote: > > > Heya Everyone, > > > > I recently gave a presentation to my work colleagues on the > wonders of the > > Boost library. [snip] > > Matt, > > I don't know if you plan to keep this updated, but here is > some feedback > from a co-worker. I have not verified his findings. > [snip] > > > > The rest of the pages have the classic boost downfall: they > > don't discuss any of the pitfalls, performance problems, or > > code bloat issues, which frankly, seem like the "crazy aunt > > in the basement" of boost. > I don't suppose your co-worker would like to enlighten us about these issues/areas with which he obviously has some expertise and considers the documentation (and the code?) deficient? That would be as useful as Matt's overview could be to those just getting into/considering using boost libs. As it stands, all that the above statement adds is FUD. Regards Darryl Green ########################################################################## This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimise the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. ##########################################################################

3 2

Library array
by Dave 11 Nov '03

11 Nov '03

Hello all, I have recently reviewed the Boost presentation put together by Matthew and intend to present it to my peers also. It was especially welcome to see this because I've been wanting to present to my peers on Boost for awhile but haven't had the time to learn enough about the library to put a presentation together. So, something I wanted fell right in my lap! Kinda like finding a $100 bill on the street! I do have one question about the array library. In the documentation, the statement is made that the advantage array has over vector is the fact that since vectors provide the semantics of dynamic arrays, "This results in some overhead in case only arrays with static sizes are needed.". When discussing this with my peers, I'd like to present something a little more concrete to them. If I have a number of elements that is known at compile time, why, *specifically*, should I prefer boost::array to std::vector? Thanks! Dave

2 2

problem with versio 1_30_0
by S.M. Sohelozzaman 11 Nov '03

11 Nov '03

Hello all, I am a new member of this group and I am facing some problems with the new boost version. I was trying to compile and link my old C++ codes with the new boost version (1_30_0 and 1_30_2). It compiles but during the linking time it gives the following errors: ======================================================= Boost Root = /home/sohel/projects/boost_1_30_0 Applications lib: /home/sohel/projects/boost_1_30_0/libs/thread/build/bin/libboost_thread.so/gcc/debug/runtime-link-dynamic/shared-linkable-true/threading-multi/libboost_threadd.so NT: boost: 30 ...patience... don't know how to make /home/sohel/projects/boost_1_30_0/libs/thread/build/bin/libboost_thread.so/gcc/debug/runtime-link-dynamic/shared-linkable-true/threading-multi/libboost_threadd.a ...found 390 targets... ...can't find 1 target... ...can't make 7 targets... ...skipped 000_easy_positioning for lack of /home/sohel/projects/boost_1_30_0/libs/thread/build/bin/libboost_thread.so/gcc/debug/runtime-link-dynamic/shared-linkable-true/threading-multi/libboost_threadd.a... ======================================================= Please help me with the ideas how I can solve this problem. Thanks in advance. Sohel. __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree

1 0

Re: [Boost-users] Re: Note for Python 2.3 users
by Paul Grenyer 11 Nov '03

11 Nov '03

> "Paul Grenyer" <paul(a)paulgrenyer.co.uk> writes: Hi > > I assume this means I need to use Python 2.2.3 or lower, right? > > I recommend posting Boost.Python questions to the C++-sig: > http://www.boost.org/more/mailing_lists.htm#cplussig Thanks, I've joined. > and I also recommend using the CVS version of Boost.Python, which is > Python-2.3 compatible. Thanks, getting it now. Regards Paul Please note the change of email address! Paul Grenyer Email: paul(a)paulgrenyer.co.uk Web: www.paulgrenyer.co.uk

1 0

RE: [Boost-users] Library array
by Ben Hutchings 11 Nov '03

11 Nov '03

Dave <better_cs_now(a)yahoo.com> wrote: <snip> > I do have one question about the array library. In the > documentation, the statement is made that the advantage array has > over vector is the fact that since vectors provide the semantics > of dynamic arrays, "This results in some overhead in case only > arrays with static sizes are needed.". When discussing this with > my peers, I'd like to present something a little more concrete to > them. > > If I have a number of elements that is known at compile time, why, > *specifically*, should I prefer boost::array to std::vector? The array is stored inside the class instance rather than separately allocated from the heap. There is no need for additional pointer and size member data. This saves time and memory. Many member functions are trivial because of the fixed size. This also saves time. The array size is exactly what you specify, whereas std::vector may round up the size of its internal array to allow for some growth. This saves memory. There may also be a reduction in mental overhead because you will never have to think about the possibility of the array size changing. One disadvantage is that you can catch a failed heap allocation whereas a failed automatic allocation is normally fatal. Allocating large arrays in automatic storage remains a bad idea. Ben.

3 5

RE: [Boost-users] date_time: why invalid_time_label in process_local_dst_start_day()
by Ben Hutchings 11 Nov '03

11 Nov '03

Michael Haubenwallner <michael.haubenwallner(a)salomon.at>: > as i could not google out an answer for my problem with > boost/date_time/dst_rules.hpp: is there a reason why > "boost::date_time::dst_calculator::process_local_dst_start_day()" > returns "invalid_time_label" for the transition time, but > "process_local_dst_end_day()" returns "ambigous" ? > Or is it just a bug ? At the start of DST, the time goes directly from, say, 1:00 to 2:00, so there is *no* point in time labelled 1:30 and it is invalid. At the end of DST, the time goes directly from, say, 2:00 to 1:00, so there are two points in time labelled 1:30 and it is ambiguous.

1 0

date_time: why invalid_time_label in process_local_dst_start_day()
by Michael Haubenwallner 11 Nov '03

11 Nov '03

Hello, as i could not google out an answer for my problem with boost/date_time/dst_rules.hpp: is there a reason why "boost::date_time::dst_calculator::process_local_dst_start_day()" returns "invalid_time_label" for the transition time, but "process_local_dst_end_day()" returns "ambigous" ? Or is it just a bug ? Thanks, Michael Haubenwallner -- Michael Haubenwallner SALOMON Automation GmbH Forschung & Entwicklung A-8114 Friesach bei Graz mailto:michael.haubenwallner@salomon.at http://www.salomon.at

1 0

Boost Python: Beyond handles
by Paul Grenyer 11 Nov '03

11 Nov '03

Hi All I'm trying to embed the python interpreter in a C++ program so that users can write simple scripts that can be executed when the program runs. I've been following the "Using the the Interpretter" examples an dhave had quite a lot of success, except with this one: handle<> main_module(borrowed( PyImport_AddModule("__main__") )); handle<> main_namespace(borrowed( PyModule_GetDict(main_module.get ()) )); handle<> main_module( borrowed( PyImport_AddModule("__main__") )); main_namespace dict(handle<>(borrowed( PyModule_GetDict(main_module.get ()) ))); handle<>( PyRun_String(" result = 5 ** 2", Py_file_input, main_namespace.ptr(), main_namespace.ptr()) ); int five_squared = extract<int>( main_namespace["result"] ); I'm using boost 1.30.0 and MSVC 7.1, along with the following warning (?!!): builtin_converters.hpp(114) : warning C4267: 'argument' : conversion from 'size_t' to 'int', possible loss of data I get the following errors: error C2146: syntax error : missing ';' before identifier 'dict' error C2039: 'ptr' : is not a member of 'boost::python::handle<>' error C2039: 'ptr' : is not a member of 'boost::python::handle<>' error C2676: binary '[' : 'boost::python::handle<>' does not define this operator or a conversion to a type acceptable to the predefined operator The "missing ';' before identifier 'dict'" error I can understand and I ppear to be able to fix by swapping "main_namespace" for "handle<>". I can also fix the "'ptr' : is not a member of 'boost::python::handle<>'" error by changing ptr to get. However, the final error has me stumped. Any suggestions appreciated. Regards Paul Please note the change of email address! Paul Grenyer Email: paul(a)paulgrenyer.co.uk Web: www.paulgrenyer.co.uk

2 1

Note for Python 2.3 users
by Paul Grenyer 11 Nov '03

11 Nov '03

Hi All I'm just about to start trying to use Boost.Python for the first time and noticed the following note in the docs: Note for Python 2.3 users This is a bugfix release only, and is not compatible with Python 2.3. Boost 1.31.0, which will be compatible with Python 2.3, is due out shortly. I assume this means I need to use Python 2.2.3 or lower, right? Regards Paul Please note the change of email address! Paul Grenyer Email: paul(a)paulgrenyer.co.uk Web: www.paulgrenyer.co.uk

2 1

'long long' problem on VC++7.1
by Nick Savoiu 11 Nov '03

11 Nov '03

I'm trying to compile some boost code on VC+7.1 but I get: e:\users\savoiu\Projects\boost-1.30.2\boost\concept_check.hpp(183) : error C2632: 'long' followed by 'long' is illegal Do I need any #defines when using Boost with VC++7.1 or should it work right out of the box? Thanks, Nick

2 2

Compiler command line options...
by Soumitra Chatterjee 10 Nov '03

10 Nov '03

Hi, I am a newbie, and I have a very basic question regarding compilation of boost libraries. Setup: I am using the bjam setup to build and test the boost library. I use something like $ cd <boost-root> $ bjam -a "-sTOOLS=acc" to try and build the library. Problem: I would like to add some compiler options (eg -myopt) during the build. How and where do I add them? Thanks in advance. -- Soumitra

2 1

Problem with installing Boost man
by Alex Vinokur 09 Nov '03

09 Nov '03

Hi, I have got a problem while installing man, =========================================== Windows 2000 Professional CYGWIN_NT-5.0 1.5.4(0.94/3/2) =========================================== $ tar -xf boost_1_30_doc_man.tar tar: boost_1_30_0/doc/man/man3/boost\:\:any.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:any_cast.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:bad_any_cast.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:bad_function_call.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:function.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:functionN.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:function_base.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:is_reference_wrapper.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:last_value.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:reference_wrapper.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:signal.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:signalN.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:signals\:\:connection.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:signals\:\:scoped_connection.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:signals\:\:trackable.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:slot.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:unwrap_reference.3: Cannot open: No such file or directory tar: boost_1_30_0/doc/man/man3/boost\:\:visit_each.3: Cannot open: No such file or directory tar: Error exit delayed from previous errors What is wrong? ===================================== Alex Vinokur mailto:alexvn@connect.to http://mathforum.org/library/view/10978.html news://news.gmane.org/gmane.comp.lang.c++.perfometer =====================================

2 1

c_grammar example
by adel.essafi 09 Nov '03

09 Nov '03

hi list I have a problem with spirit library. when I try to compile the c_grammar example , it takes to me 5 hours!!!!!! it s foolish. do you have the same problem please! cheers Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34/mn) ; tél : 08 92 68 13 50 (0,34/mn)

3 2

BOOST_HAS_THREADS
by Lalit Seth 09 Nov '03

09 Nov '03

Hi all, I was using a a boost library boost_1_30_0. now i tried to use new boost realease boost-1.30.2. But compiling the same application with new boost library results in error Thread support is unavailable! as BOOST_HAS_THREADS Macro is not defined. This is wht i have doen to install boost under RedHat8.0 Linux ./configure bjam How can i rectify it? Rgds Lalit _________________________________________________________________ Pinjar is a classic! Check out the making of this film. http://server1.msn.co.in/sp03/Pinjar/index.asp Simply click here!

3 2

Re: [Boost-users] BOOST_HAS_THREADS
by Lalit Seth 09 Nov '03

09 Nov '03

This is not wrking bjam -sBUILD="<define>_REENTRANT <threading>multi" > Help me Ists urgent? >From: cavok(a)filibusta.crema.unimi.it (Domenico Andreoli) >Reply-To: Boost Users mailing list <boost-users(a)lists.boost.org> >To: boost-users(a)lists.boost.org >Subject: Re: [Boost-users] BOOST_HAS_THREADS >Date: Sat, 8 Nov 2003 17:12:43 +0100 > >On Sat, Nov 08, 2003 at 01:26:37PM +0530, Lalit Seth wrote: > > Hi all, > > >hi > > > I was using a a boost library boost_1_30_0. > > now i tried to use new boost realease boost-1.30.2. > > > > But compiling the same application with new boost library results in >error > > Thread support is unavailable! > > > > as BOOST_HAS_THREADS Macro is not defined. > > > > This is wht i have doen to install boost under RedHat8.0 Linux > > > > ./configure > > bjam > > >i think i've solved invoking bjam this way: >bjam -sBUILD="<define>_REENTRANT <threading>multi" > >ciao >dom > >-----[ Domenico Andreoli, aka cavok > --[ http://filibusta.crema.unimi.it/~cavok/gpgkey.asc > ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 >_______________________________________________ >Boost-users mailing list >Boost-users(a)lists.boost.org >http://lists.boost.org/mailman/listinfo.cgi/boost-users _________________________________________________________________ Discover digital jadoo! Enter this contest. http://server1.msn.co.in/sp03/mediacenter/index.asp Win cool prizes!

2 1

MultiArray - issue with views and striding
by Ronald Garcia 08 Nov '03

08 Nov '03

Nasatyr, Ben (London) wrote: > Suppose I have a 1d-array of size 10 (index base is 0). If I create a view > on [0,10), strided by 3, shouldn't the size of the result be 4, > corresponding to indices 0, 3, 6 and 9? Instead I get 3. Hi, It appears you have correctly diagnosed a bug in the code for views. Thank you. I will check a fix into the Boost CVS. Cheers, ron

1 0

2 bind questions
by Angus Leeming 07 Nov '03

07 Nov '03

I'm having some problems with bind and wonder if someone might help. The attached file compiles and runs fine when compiled with boost-1.30.2 (g++ 3.2 on a PC and g++ 3.3 on a Dec Alpha, both running linux). However, compilation fails if I uncomment the overloaded 'node' member function below. struct FEM { typedef std::vector<Node>::size_type size_type; FEM(std::vector<Node> const & nodes) : nodes_(nodes) {} size_type nnodes() const { return nodes_.size(); } Node & node(size_type i) { return nodes_[i]; } // Node const & node(size_type i) const { return nodes_[i]; } private: std::vector<Node> nodes_; }; boost/boost-1.30.2/boost/function/function_template.hpp:117: could not convert `f->boost::_bi::bind_t<R, F, L>::operator()(A1&) [with A1 = size_t, R = const Node&, F = boost::_mfi::cmf1<const Node&, FEM, unsigned int>, L = boost::_bi::list2<boost::reference_wrapper<FEM>, boost::arg<1> >]((&a0))' to `Node&' Is there a fix for this or have I hit a brick wall? Second question. I'd like to combine these two boost::functions into a single boost::function2<void, size_t, double> all_in_one = ...; all_in_one(i, val); but I'm getting horribly lost trying to determine the '...'. Is it possible? Any clues? Kind regards, Angus ps. What is the prefered way of posting code? Inline or as an attachment? A std::vector<Node> nodes(10); FEM fem(nodes); size_t i = 5; double const val = 14; boost::function1<Node &, size_t> get_node = boost::bind(&FEM::node, boost::ref(fem), _1); boost::function1<void, double> set_value = boost::bind(&Node::set_conc, boost::ref(get_node(i)), _1); set_value(val);

2 2

RE: [Boost-users] Re: shared_ptr compiler error with gcc
by Ben Hutchings 06 Nov '03

06 Nov '03

amerio <amerio(a)hotmail.com> wrote: > > Does Nintendo not supply a newer version? Do they even support the > > standard library (which Boost is somewhat dependent on)? > > Actually, it is gcc 2.95.3 > The stl is supported via the latest stlport. <snip> > > This error message seems to be incomplete. > > oops. here it is : > boost/detail/shared_count.hpp: > In method `void * > boost::detail::sp_counted_base_impl<P,D>::get_deleter(const type_info > &)': Internal compiler error. > > If anyone was successful compiling this on the gamecube, > please share your knowledge ! > (boost 1.30.2, gcc 2.95.3 with prodg for gamecube) I think you have disabled RTTI, so the call to typeid() does not work. There is a bug in 2.95.3 that causes it to fail rather than reporting this error in a helpful way: <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3689>. If you remove the option '-fno-rtti' from the compiler command line it should work.

1 0

RE: [Boost-users] Problems with call_traits in GCC 3.2 20020927(prerelease)
by Ben Hutchings 06 Nov '03

06 Nov '03

Joaquín Mª López Muñoz <joaquin(a)tid.es> wrote: > The following programs does not compile with error > > foo.cpp: In function `int main()': > foo.cpp:11: no matching function for call to `foo(std::string)' > > Program code: > > #include <boost/call_traits.hpp> > #include <string> > > template<typename Type> > void foo(typename boost::call_traits<Type>::param_type x) > { > } > > int main() > { > foo(std::string("bar")); > > return 0; > } > > > Environment is GCC 3.2 20020927 (prerelease) under Cygwin. > Anyvody run into a similar problem? Workarounds, ideas? Thanx > in advance. This is standard behaviour. See my explanation in <http://groups.google.com/groups?selm=slrnbisehj.1pc.do-not-spam-benh%40tin.…>. Without knowing what it is you are trying to do, I cannot offer a workaround.

3 2

RE: [Boost-users] Problems with call_traits in GCC3.220020927(prerelease)
by Ben Hutchings 06 Nov '03

06 Nov '03

Joaquín Mª López Muñoz <joaquin(a)tid.es> wrote: > Ben Hutchings ha escrito: <snip> > > Without knowing what it is you are trying to do, I cannot offer > > a workaround. > > With pleasure. My original design was > > template<typename Type> > void foo(const Type& x) > { > } > > (of course the actual code does something useful) > and I wanted to take advantage of the call_traits<>::param_type > optimization for basic types. > > So, no way? Should I revert to const Type&? Some clever workaround > to help the compiler swallow the construct? Thx in advance. I would leave it as const Type &. If you think your compiler is not smart enough to make a local copy of what x refers to when Type when that's likely to improve performance, you could use something like this: template<typename Type> void foo(const Type & arg_x) { typename boost::call_traits<Type>::param_type local_x = arg_x; ... }

1 0

date_time library problem
by Istvan Buki 06 Nov '03

06 Nov '03

Hello, here is a small piece of code that use the posix_time system that fails to compile. I'm wondering whether it is a bug in the library or my usage of the library that is wrong. Thank you for your help. Istvan #include "boost/date_time/posix_time/posix_time.hpp" #include <iostream> int main() { using namespace boost::posix_time ; ptime now = microsec_clock::local_time(); std::cout << to_simple_string( now ) << std::endl ; return 0 ; } g++ -I/opt/boost brol.cpp /tmp/ccQQjwdW.o(.gnu.linkonce.t._ZN5boost9date_time15month_formatterINS_9gregorian10greg_monthENS0_13simple_formatEE12format_monthERKS3_RSo+0x3a): In function `boost::date_time::month_formatter<boost::gregorian::greg_month, boost::date_time::simple_format>::format_month(boost::gregorian::greg_month const&, std::basic_ostream<char, std::char_traits<char> >&)': : undefined reference to `boost::gregorian::greg_month::as_short_string() const' /tmp/ccQQjwdW.o(.gnu.linkonce.t._ZN5boost9date_time15month_formatterINS_9gregorian10greg_monthENS0_13simple_formatEE12format_monthERKS3_RSo+0x5c): In function `boost::date_time::month_formatter<boost::gregorian::greg_month, boost::date_time::simple_format>::format_month(boost::gregorian::greg_month const&, std::basic_ostream<char, std::char_traits<char> >&)': : undefined reference to `boost::gregorian::greg_month::as_long_string() const' collect2: ld returned 1 exit status The system is running SuSE linux 9.0 compiler: gcc 3.3.1 boost version 1.30.2

2 1

RE: [Boost-users] date_time library problem
by Ben Hutchings 06 Nov '03

06 Nov '03

Istvan Buki <istvan.buki(a)euronet.be> wrote: > here is a small piece of code that use the posix_time system that > fails to compile. > I'm wondering whether it is a bug in the library or my usage of the > library that is wrong. <snip> Library code normally needs to be compiled separately into a library file that is then statically or dynamically linked with the client code. Boost is unusual in that many of its libraries contain only inline and template functions that are compiled along with the client code. However, the date_time, filesystem, graph, python, regex, signals, test, and thread libraries have some code that must be separately compiled. See the file tools/build/index.html in the Boost distribution or on www.boost.org.

1 0

RE: [Boost-users] shared_ptr compiler error with gcc
by Ben Hutchings 06 Nov '03

06 Nov '03

amerio <amerio(a)hotmail.com> wrote: > I'm trying to compile a gamecube sample with boost_1_30_2 and gcc > version egcs-2.91.57 (nintendo package): That's a very old version of GCC. Boost isn't tested with anything older than version 2.95.3, and that only on Linux, with a 41% failure rate. (See <http://boost.sourceforge.net/regression-logs/> for the details.) Does Nintendo not supply a newer version? Do they even support the standard library (which Boost is somewhat dependent on)? There are unofficial builds of GCC 3.x (which Boost works well with) for the Gamecube though I don't know whether they include libstdc++. Google for "gcc gamecube" and you'll find them. > #include <boost/shared_ptr.hpp> > int main() > { > boost::shared_ptr<int> i ( new int ); > } > > I got: > boost/detail/shared_count.hpp: > In method `void * > boost::detail::sp_counted_base_impl<P,D>::get_deleter(const This error message seems to be incomplete.

2 1

libraries based on Boost
by Mohamed Iqbal 06 Nov '03

06 Nov '03

Hi... Is there any library that is based on Boost but not a part of it? Mohammed

2 1

Problems with call_traits in GCC 3.2 20020927 (prerelease)
by Joaquín Mª López Muñoz 06 Nov '03

06 Nov '03

The following programs does not compile with error foo.cpp: In function `int main()': foo.cpp:11: no matching function for call to `foo(std::string)' Program code: #include <boost/call_traits.hpp> #include <string> template<typename Type> void foo(typename boost::call_traits<Type>::param_type x) { } int main() { foo(std::string("bar")); return 0; } Environment is GCC 3.2 20020927 (prerelease) under Cygwin. Anyvody run into a similar problem? Workarounds, ideas? Thanx in advance. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

MultiArray - issue with views and striding.
by Nasatyr, Ben (London) 06 Nov '03

06 Nov '03

Can anyone help shed light on the following? Suppose I have a 1d-array of size 10 (index base is 0). If I create a view on [0,10), strided by 3, shouldn't the size of the result be 4, corresponding to indices 0, 3, 6 and 9? Instead I get 3. Please forgive me if I'm off the mark here, as I'm new to boost in general and MultiArray in particular. The relevant line (assuming len => size) in boost/multi_array/base.hpp seems to be index len = (finish - start) / index_factor; (boost::detail::multi_array::multi_array_impl_base<>::generate_array_view() line 427). I would have written index len = 1 + (finish - 1 - start) / index_factor; The following code sample should make all clear. Any clarification greatly appreciated. Cheers, Ben typedef boost::multi_array<double, 1> array_type; typedef array_type::index index; typedef array_type::index_range range; index i; int values = 0; // Setup our base array and data. // A is a 1-d array with size 10, indices 0,1,...,9 and values 0,1,...,9. array_type A(boost::extents[10]); for(i = 0; i != 10; ++i) A[i] = values++; for(i = 0; i != 10; ++i) assert(A[i]==i); assert(A.size()==10); // The following views of A should all be effectively the same, // corresponding to indices 0,3,6,9 of A, so having // size 4, indices 0,1,2,3 and values 0,3,6,9? array_type::array_view<1>::type view1 = A[boost::indices[range(0,12,3)] ]; array_type::array_view<1>::type view2 = A[boost::indices[range(0,11,3)] ]; array_type::array_view<1>::type view3 = A[boost::indices[range(0,10,3)] ]; for(i = 0; i != 4; ++i) { assert(A[i*3]==view1[i]); assert(A[i*3]==view2[i]); assert(A[i*3]==view3[i]); } assert(view1.size()==4); assert(view2.size()==4); // Assert fails!? assert(view3.size()==4); // Assert fails!?

1 0

Re: [Boost-users] RE: LNK2019 errors in when compiling vc7 project
by cyril.godart＠bnpparibas.com 06 Nov '03

06 Nov '03

You need only to reference one library depending on your Settings->C/C++->Code Generation:Use run-time library value. The extension should tell you right away which version it is you need. Internet eyebe97@yahoo.com@lists.boost.org - 05/11/2003 21:52 Please respond to boost-users(a)lists.boost.org Sent by: boost-users-bounces(a)lists.boost.org To: boost-users cc: Subject: [Boost-users] RE: LNK2019 errors in when compiling vc7 project I figured out the problem. I had already built the boost libraries. And had specified the location (directory) of the libraries in Linker--> General--> Additional Library Directories field. To get my project to compile, I listed every boost library in the Linker--> Input --> Additional Dependancies field. Linker--> Input --> Additional Dependancies: C:\cpp\boost\libs\regex\build\vc7-stlport\boost_regex_vc7-stlport_mdidd.lib C:\cpp\boost\libs\regex\build\vc7-stlport\boost_regex_vc7-stlport_mdid.lib C:\cpp\boost\libs\regex\build\vc7-stlport\boost_regex_vc7-stlport_mdi.lib etc... Thanks for your help, Cyril Please respond to boost-users(a)lists.boost.org Sent by: boost-users-bounces(a)lists.boost.org To: boost-users cc: Subject: [Boost-users] LNK2019 errors in when compiling vc7 project using Regex I'm having a problem building my VS .NET C++ Console Application. One of the classes uses the Boost RegEx++ libraries. If I compile the class by itself, I get no errors. If I build the project, I get the 15 linking errors (3 are included at the bottom of this message) and they all refer to regex++ calls. I pretty sure that my problem is that the correct regex library, dll, or class is not specified in the correct properties setting , but I have no clue where the specification needs to go. Please Help!! Project settings: C/C++ --> General --> Additional Include Directories: "C:\cpp\STLport-4.6\stlport";C:\cpp\boost Linker --> General --> Additional Library Directories: C:\cpp\boost\libs\regex\build\vc7-stlport 3 of 15 linking errors Prob.obj : error LNK2019: unresolved external symbol "public: __thiscall boost::reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >::~reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >(void)" (??1?$reg_expression@DV?$regex_traits@D@boost@@V?$allocator@D@_STL@@@boost@@QAE@XZ) referenced in function "public: virtual void __thiscall Prob::main(char * const,struct diff *,bool)" (?main@Prob@@UAEXQADPAUdiff@@_N@Z) Prob.obj : error LNK2019: unresolved external symbol "public: __thiscall boost::reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >::reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >(char const *,unsigned int,class _STL::allocator<char> const &)" (??0?$reg_expression@DV?$regex_traits@D@boost@@V?$allocator@D@_STL@@@boost@@QAE@PBDIABV?$allocator@D@_STL@@@Z) referenced in function "public: virtual void __thiscall Prob::main(char * const,struct diff *,bool)" (?main@Prob@@UAEXQADPAUdiff@@_N@Z) Prob.obj : error LNK2019: unresolved external symbol "protected: void __cdecl boost::re_detail::match_results_base<char const *,class _STL::allocator<char> >::m_free(void)" (?m_free@?$match_results_base@PBDV?$allocator@D@_STL@@@re_detail@boost@@IAAXXZ) referenced in function "public: __thiscall boost::re_detail::match_results_base<char const *,class _STL::allocator<char> >::~match_results_base<char const *,class _STL::allocator<char> >(void)" (??1?$match_results_base@PBDV?$allocator@D@_STL@@@re_detail@boost@@QAE@XZ) __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. --------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.

1 0

shared_ptr compiler error with gcc
by amerio 06 Nov '03

06 Nov '03

Hi, I'm trying to compile a gamecube sample with boost_1_30_2 and gcc version egcs-2.91.57 (nintendo package): #include <boost/shared_ptr.hpp> int main() { boost::shared_ptr<int> i ( new int ); } I got: boost/detail/shared_count.hpp: In method `void * boost::detail::sp_counted_base_impl<P,D>::get_deleter(const

1 0

RE: LNK2019 errors in when compiling vc7 project
by i b 05 Nov '03

05 Nov '03

I figured out the problem. I had already built the boost libraries. And had specified the location (directory) of the libraries in Linker--> General--> Additional Library Directories field. To get my project to compile, I listed every boost library in the Linker--> Input --> Additional Dependancies field. Linker--> Input --> Additional Dependancies: C:\cpp\boost\libs\regex\build\vc7-stlport\boost_regex_vc7-stlport_mdidd.lib C:\cpp\boost\libs\regex\build\vc7-stlport\boost_regex_vc7-stlport_mdid.lib C:\cpp\boost\libs\regex\build\vc7-stlport\boost_regex_vc7-stlport_mdi.lib etc... Thanks for your help, Cyril Please respond to boost-users(a)lists.boost.org Sent by: boost-users-bounces(a)lists.boost.org To: boost-users cc: Subject: [Boost-users] LNK2019 errors in when compiling vc7 project using Regex I'm having a problem building my VS .NET C++ Console Application. One of the classes uses the Boost RegEx++ libraries. If I compile the class by itself, I get no errors. If I build the project, I get the 15 linking errors (3 are included at the bottom of this message) and they all refer to regex++ calls. I pretty sure that my problem is that the correct regex library, dll, or class is not specified in the correct properties setting , but I have no clue where the specification needs to go. Please Help!! Project settings: C/C++ --> General --> Additional Include Directories: "C:\cpp\STLport-4.6\stlport";C:\cpp\boost Linker --> General --> Additional Library Directories: C:\cpp\boost\libs\regex\build\vc7-stlport 3 of 15 linking errors Prob.obj : error LNK2019: unresolved external symbol "public: __thiscall boost::reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >::~reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >(void)" (??1?$reg_expression@DV?$regex_traits@D@boost@@V?$allocator@D@_STL@@@boost@@QAE@XZ) referenced in function "public: virtual void __thiscall Prob::main(char * const,struct diff *,bool)" (?main@Prob@@UAEXQADPAUdiff@@_N@Z) Prob.obj : error LNK2019: unresolved external symbol "public: __thiscall boost::reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >::reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >(char const *,unsigned int,class _STL::allocator<char> const &)" (??0?$reg_expression@DV?$regex_traits@D@boost@@V?$allocator@D@_STL@@@boost@@QAE@PBDIABV?$allocator@D@_STL@@@Z) referenced in function "public: virtual void __thiscall Prob::main(char * const,struct diff *,bool)" (?main@Prob@@UAEXQADPAUdiff@@_N@Z) Prob.obj : error LNK2019: unresolved external symbol "protected: void __cdecl boost::re_detail::match_results_base<char const *,class _STL::allocator<char> >::m_free(void)" (?m_free@?$match_results_base@PBDV?$allocator@D@_STL@@@re_detail@boost@@IAAXXZ) referenced in function "public: __thiscall boost::re_detail::match_results_base<char const *,class _STL::allocator<char> >::~match_results_base<char const *,class _STL::allocator<char> >(void)" (??1?$match_results_base@PBDV?$allocator@D@_STL@@@re_detail@boost@@QAE@XZ) __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree

1 0

Re: [Boost-users] LNK2019 errors in when compiling vc7 project using Regex
by cyril.godart＠bnpparibas.com 05 Nov '03

05 Nov '03

Hi, It seems that you simply have not linked to the regex library. BTW, I believe the name is "regex" and that "Regex++" was the name before John Maddock ported his library to boost. Regex is one of boost library that does not consist only of headers. It needs an actual binary to link to. Which means you have to build it yourself. Have you gone through this stage ? If not I suggest you do not go through Bjam for this one and instead go to boost/libs/regex/build and run the VC7 make file there (vc7) inside the VC7 command console. If memory serves, it produces the complete set of static and dynamic libraries you need whereas Bjam does only part of it (or maybe I could not make it work properly). Then in your settings in the link tab put the path to the library you want to use (I believe a pragma lib takes care of choosing the one compatible with the version of the C library you compile with). Kind regards, Cyril Godart. Internet eyebe97@yahoo.com@lists.boost.org - 04/11/2003 20:42 Please respond to boost-users(a)lists.boost.org Sent by: boost-users-bounces(a)lists.boost.org To: boost-users cc: Subject: [Boost-users] LNK2019 errors in when compiling vc7 project using Regex I'm having a problem building my VS .NET C++ Console Application. One of the classes uses the Boost RegEx++ libraries. If I compile the class by itself, I get no errors. If I build the project, I get the 15 linking errors (3 are included at the bottom of this message) and they all refer to regex++ calls. I pretty sure that my problem is that the correct regex library, dll, or class is not specified in the correct properties setting , but I have no clue where the specification needs to go. Please Help!! Project settings: C/C++ --> General --> Additional Include Directories: "C:\cpp\STLport-4.6\stlport";C:\cpp\boost Linker --> General --> Additional Library Directories: C:\cpp\boost\libs\regex\build\vc7-stlport 3 of 15 linking errors Prob.obj : error LNK2019: unresolved external symbol "public: __thiscall boost::reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >::~reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >(void)" (??1?$reg_expression@DV?$regex_traits@D@boost@@V?$allocator@D@_STL@@@boost@@QAE@XZ) referenced in function "public: virtual void __thiscall Prob::main(char * const,struct diff *,bool)" (?main@Prob@@UAEXQADPAUdiff@@_N@Z) Prob.obj : error LNK2019: unresolved external symbol "public: __thiscall boost::reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >::reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >(char const *,unsigned int,class _STL::allocator<char> const &)" (??0?$reg_expression@DV?$regex_traits@D@boost@@V?$allocator@D@_STL@@@boost@@QAE@PBDIABV?$allocator@D@_STL@@@Z) referenced in function "public: virtual void __thiscall Prob::main(char * const,struct diff *,bool)" (?main@Prob@@UAEXQADPAUdiff@@_N@Z) Prob.obj : error LNK2019: unresolved external symbol "protected: void __cdecl boost::re_detail::match_results_base<char const *,class _STL::allocator<char> >::m_free(void)" (?m_free@?$match_results_base@PBDV?$allocator@D@_STL@@@re_detail@boost@@IAAXXZ) referenced in function "public: __thiscall boost::re_detail::match_results_base<char const *,class _STL::allocator<char> >::~match_results_base<char const *,class _STL::allocator<char> >(void)" (??1?$match_results_base@PBDV?$allocator@D@_STL@@@re_detail@boost@@QAE@XZ) __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. --------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.

1 0

LNK2019 errors in when compiling vc7 project using Regex
by i b 04 Nov '03

04 Nov '03

I'm having a problem building my VS .NET C++ Console Application. One of the classes uses the Boost RegEx++ libraries. If I compile the class by itself, I get no errors. If I build the project, I get the 15 linking errors (3 are included at the bottom of this message) and they all refer to regex++ calls. I pretty sure that my problem is that the correct regex library, dll, or class is not specified in the correct properties setting , but I have no clue where the specification needs to go. Please Help!! Project settings: C/C++ --> General --> Additional Include Directories: "C:\cpp\STLport-4.6\stlport";C:\cpp\boost Linker --> General --> Additional Library Directories: C:\cpp\boost\libs\regex\build\vc7-stlport 3 of 15 linking errors Prob.obj : error LNK2019: unresolved external symbol "public: __thiscall boost::reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >::~reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >(void)" (??1?$reg_expression@DV?$regex_traits@D@boost@@V?$allocator@D@_STL@@@boost@@QAE@XZ) referenced in function "public: virtual void __thiscall Prob::main(char * const,struct diff *,bool)" (?main@Prob@@UAEXQADPAUdiff@@_N@Z) Prob.obj : error LNK2019: unresolved external symbol "public: __thiscall boost::reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >::reg_expression<char,class boost::regex_traits<char>,class _STL::allocator<char> >(char const *,unsigned int,class _STL::allocator<char> const &)" (??0?$reg_expression@DV?$regex_traits@D@boost@@V?$allocator@D@_STL@@@boost@@QAE@PBDIABV?$allocator@D@_STL@@@Z) referenced in function "public: virtual void __thiscall Prob::main(char * const,struct diff *,bool)" (?main@Prob@@UAEXQADPAUdiff@@_N@Z) Prob.obj : error LNK2019: unresolved external symbol "protected: void __cdecl boost::re_detail::match_results_base<char const *,class _STL::allocator<char> >::m_free(void)" (?m_free@?$match_results_base@PBDV?$allocator@D@_STL@@@re_detail@boost@@IAAXXZ) referenced in function "public: __thiscall boost::re_detail::match_results_base<char const *,class _STL::allocator<char> >::~match_results_base<char const *,class _STL::allocator<char> >(void)" (??1?$match_results_base@PBDV?$allocator@D@_STL@@@re_detail@boost@@QAE@XZ) __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree

1 0

Is threads CodeWarrior project broken?
by Steve Folly 04 Nov '03

04 Nov '03

Hi, I'm trying to build the threads library on Codewarrior with the .mcp project supplied in libs/thread/build/ (using CW9, OS X 10.2.8), but Codewarrior says the file is not a project file. Is it broken? I could probably recreate it, but I'm not sure about about what source files to include for the Mac - there's all the extra stuff under src/mac/ and then what about the src/mac/msl_replacements/ stuff? Any help gratefully received. I'd like to do a multi-target project for Mac and Win32; tips for source files for Win32 would be helpful too. Thanks. Steve.

5 6

RE: [Boost-users] [BLL] How to search in a list for an object comparing a data member?
by Ben Hutchings 01 Nov '03

01 Nov '03

Gianluca Silvestri <gianluca.silvestri(a)maior.it> wrote: > Hi all, > What I want to achieve is a code similar to this: > > struct Foo { int fDataMember;} > > int main() > { > std::vector<Foo> foos; > Foo fo; > std::find_if(foos.begin(), foos.end(), _1->fDataMember == > fo.fDataMember); //<-- won't compile; } Well, apart from the missing semi-colon, missing includes and missing closing brace, I imagine you're having trouble with "_1->fDataMember". This is a documented limitation of the lambda library - there is no way to defer lookup of member names (overloading -> just changes the type and value of the pointer used) so member access can't be done on a placeholder. > I know I could use a functor object but this is just an example for a > more general need. Sorry, you'll have to define functors. These template functor classes might be useful: template<typename C, typename V, const V C::* P> struct lookup_member_const { const V & operator()(const C & c) const { return c.*P; } }; template<typename C, typename V, V C::* P> struct lookup_member { V & operator()(C & c) const { return c.*P; } }; Mind you, there might be similar things in Boost already.

4 3

Build+Install+/Zc:wchar_t in Visual studio builds
by John Maddock 01 Nov '03

01 Nov '03

Guys, Rene's new Install code is working very well for me now, but I have a question about how we're building with Visual Studio .NET. Currently the vc7 and vc7.1 toolsets turn on /Zc:wchar_t unconditionally when building, however this is not the default option in current versions of the IDE, and of course the two options produce binary-incompatible libraries (at least as far as regex is concerned). How should we handle this? At the very least I would like to see a bjam option to turn off /Zc:wchar_t, but how should we be building the libraries by default: turning native wchar_t support on is the standards conforming way, but not currently the default Visual Studio way, or the way many third party libraries (like ICU for example) are built. Does anyone know how this option interacts with MFC/ATL/VisualForms etc? We could of course create a new build variant to handle this, but with 8 regex lib/dll variants already I'm not keen to add another 8 (apart from anything else testing already takes too long). I'm cross posting this to the Boost.users group as well, since whatever resolution we take will affect them the most :-) Thanks, John.

3 4

[newbie] creating a (complex?) C++ wrapper around a C function call...
by Jason House 31 Oct '03

31 Oct '03

I want to create a wrapper function template <class foo> op_pk_fd_set_class(packet *packet, int index, foo &value, int simulated_bits); around the following function... (in OPNET) op_pk_fd_set( packet* pkptr, // same as in wrapper int index, // same as in wrapper int some_constant, //OPC_TYPE_STRUCT void* value, int simulated_bits, // same as in wrapper void* (*copy_proc)(void* obj_to_copy,int alloc_size), void (dealloc_proc*)(void *obj), int alloc_size); I believe dealloc_proc can just be a function pointer to the destructor. I could very well be mistaken, but I believe that a normal constructor takes only one parameter. I also think alloc_size should be sizeof(foo). I do not know how to obtain function pointers for constructor and deconstructor member functions. Any assistance I could get would be appreciated.

1 0

RE: [Boost-users] Re: Build+Install+/Zc:wchar_t in Visual studio builds
by Ben Hutchings 31 Oct '03

31 Oct '03

Edward Diener <eddielee(a)tropicsoft.com> wrote: > John Maddock wrote: > > Guys, > > > > We could of course create a new build variant to handle this, but > > with 8 regex lib/dll variants already I'm not keen to add another 8 > > (apart from anything else testing already takes too long). > > I think you have to do this John if you want to support both the C++ > wchar_t and the MS wchar_t in Boost libraries. Although there are > VC++ predefined macros, _WCHAR_T_DEFINED and _NATIVE_WCHAR_T_DEFINED, > which are defined when /Zc:wchar_t is used, they are also stupidly > defined, according to the documentation, when typedef unsigned short > wchar_t is used ( talk about idiotic MS decisions ). That appears to be a documentation bug. I checked this in VC++ 7.1 and _NATIVE_WCHAR_T_DEFINED is not defined by <cstddef>. There is no sign of a #define _NATIVE_WCHAR_T_DEFINED in the headers for version 7.0 or 7.1. > So Boost needs to use a macro which the end-programmer must define > which tells whether or not /Zc:wchar_t is being used or not, and > create another set of libraries accordingly. Even in the absence of a macro, this test works: #include <cstddef> #include <iostream> #include <ostream> #include "boost/type_traits.hpp" int main() { std::cout << "/Zc:wchar_t was "; if (!boost::is_same<wchar_t, __wchar_t>::value) std::cout << "not "; std::cout << "used\n"; }

1 0

RE: [Boost-users] vc++
by Ben Hutchings 31 Oct '03

31 Oct '03

adel.essafi <adel.essafi(a)laposte.net> wrote: > is it possible to compile boost project directly with vc++ 6.0 without > using commande lines. if yes how? Yes - in the IDE, create a "makefile" project and enter the command lines and targets in the project settings. It would be nice to have project files included in the distributed source, but unfortunately the file format is different for every IDE and for every different version of the Visual C++ IDE so it would be difficult to keep them all up-to-date. Ben.

1 0

[BLL] How to search in a list for an object comparing a data member?
by Gianluca Silvestri 31 Oct '03

31 Oct '03

Hi all, What I want to achieve is a code similar to this: struct Foo { int fDataMember;} int main() { std::vector<Foo> foos; Foo fo; std::find_if(foos.begin(), foos.end(), _1->fDataMember == fo.fDataMember); //<-- won't compile; } I know I could use a functor object but this is just an example for a more general need. Thanks, Gianluca

1 0

vc++
by adel.essafi 30 Oct '03

30 Oct '03

hi list is it possible to compile boost project directly with vc++ 6.0 without using commande lines. if yes how? thanks Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34/mn) ; tél : 08 92 68 13 50 (0,34/mn)

1 0

Linker problem using boost::regex with VC6.5
by Sven Van Echelpoel 29 Oct '03

29 Oct '03

Hi, I'm having a strange problem when I try to include boost::regex in my project (VC6.5 on Win2K). I'm not using Build to build a separate regex dll but rather include the source files directly in the project (or rather in a small utility static library). I've defined BOOST_REGEX_STATIC_LINK to avoid __declspec( dllimport ) / __declspec( dllexport ). Although everything compiles just fine the linker complains that it cannot find the library boost_regex_vc6_mdsd.lib. Further investigation revealed that it is actuallty listed somewhere as an additional default library (the linker outputs this when you switch on link progress messages). Searching through the sourcecode for #pragma comment( lib, ... ) and #pragma comment( linker, ... ) directives came up empty as did a search for boost_regex_vc6_mdsd.lib in all sources and headers. I got it to link by letting the linker ignore boost_regex_vc6_mdsd.lib. Even so I still would like to know where this is comming from. Any ideas? Sven

2 1

RE: [Boost-users] Linker problem using boost::regex with VC6.5
by Sven Van Echelpoel 29 Oct '03

29 Oct '03

Sven Van Echelpoel wrote: [...] > Are you sure that that's defined for all translation units that use or > implement Boost.Regex? Yep. Double checked it now and it is defined at the project level for every project [...] >> Searching through the sourcecode for >> #pragma comment( lib, ... ) and #pragma comment( linker, ... ) >> directives came up empty as did a search for boost_regex_vc6_mdsd.lib >> in all sources and headers. > > It's in "boost/regex/v3/regex_library_include.hpp". Found it. I can now see I need to define the guard macro BOOST_REGEX_NO_LIB to disable the auto-linking. Doing so makes everything build just fine. Thanks, Sven

1 0

CEST timezone conversion, boost date_time
by Erik Thiele 29 Oct '03

29 Oct '03

hi. i am trying to convert between UTC and CEST/CET (Europe/Berlin) i don't find documentation or suitable functions in the Wiki, the examples or the documentation. also i don't understand the sourcecode of the time zone stuff. but i found that eu_dst_trait exists, but don't know what that is and how to use it. any ideas? cu & thx erik -- Erik Thiele

2 2

Any thoughts on transparent marshalling?
by Hurd, Matthew 28 Oct '03

28 Oct '03

I wish to do some transparent marshalling... That is, via a policy, or some such, either call a function / functor returning a void or put stuff on a message queue for transportation. This is strictly asynch stuff, hence the void result or putting the message in the ether. The message queues I have in mind are tibrv, udp, tcp, shared mem, email, internal process queue... I see the serialization w.i.p. library will be useful here. Any tips on some useful boost libs / techniques to do this? Regards, Matt Hurd hurdm(a)sig.com +61.2.8226.5029

1 0

Newbie uBLAS question
by J. Scott Pendergrass 28 Oct '03

28 Oct '03

2 1

RE: [Boost-users] Linker problem using boost::regex with VC6.5
by Ben Hutchings 28 Oct '03

28 Oct '03

Sven Van Echelpoel wrote: > I'm having a strange problem when I try to include boost::regex in my > project (VC6.5 on Win2K). I'm not using Build to build a separate > regex dll but rather include the source files directly in the project > (or rather in a small utility static library). I've defined > BOOST_REGEX_STATIC_LINK to avoid __declspec( dllimport ) / __declspec( > dllexport ). Are you sure that that's defined for all translation units that use or implement Boost.Regex? > Although everything compiles just fine the linker complains that it > cannot find the library boost_regex_vc6_mdsd.lib. Further > investigation revealed that it is actuallty listed somewhere as an > additional default library (the linker outputs this when you switch > on link progress messages). Searching through the sourcecode for > #pragma comment( lib, ... ) and #pragma comment( linker, ... ) > directives came up empty as did a search for boost_regex_vc6_mdsd.lib > in all sources and headers. It's in "boost/regex/v3/regex_library_include.hpp". > I got it to link by letting the linker ignore > boost_regex_vc6_mdsd.lib. > Even so I still would like to know where this is comming from. Any > ideas? I know I had some kind of problem with the above-mentioned header generated the wrong library name when I first started using Boost.Regex so I disabled the header by defining its guard macro before including "boost/regex.hpp". However, I removed that just now and didn't have any problems. Have you created your own project definition which uses a different library name? It's probably easier just to use the makefile (vc6.mak) in Visual Studio. You can do this by selecting "Insert Project into Workspace", selecting "vc6.mak" from the build directory, and thus creating a project that calls nmake on the makefile. Then you just need to edit the project settings to specify what the target names are for each configuration.

1 0

OpenBSD
by Adam Olsen 28 Oct '03

28 Oct '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Has anyone had any luck compiling boost_regex on OpenBSD 3.3? If so, how did you do it? Thanks, Adam Olsen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/nDKyiTy1B31kxaoRAhhBAJ98+oS83jDY3kwgauPV0HN9HG5XOgCgwlpx JI8Bhk2EyKrgBn4fX72dBSk= =Owcv -----END PGP SIGNATURE-----

2 4

[spirit][newbie] few questions
by GIE 27 Oct '03

27 Oct '03

Hello! What is "proper way" of implementing result value of parser, have i implement new parser or can (and how?) i use grammar construct with user defined result value that can be passed to attached action (for ex. matched GUID returning)? What is performance penalty for using vectors (they need realloc, don't they) in ast trees? And is there anyway to store scanner defined result in tree, besides using user-specified value in node_val_data and type casting it to specific type depending of node id? Thanks. -- With best regards, GIE.

3 3

RE: [Boost-users] Boost Software License: redistribute modified works?
by Ben Hutchings 27 Oct '03

27 Oct '03

Steve M. Robbins <steven.robbins(a)videotron.ca> wrote: > I've a question for the drafters of the Boost Software > License - Version 1.0 - August 17th, 2003. I am not one of them, but I can give you some answers anyway. > Put yourself in the position of someone who wants to redistribute > a modified version of Boost. For example, the linux distributors > like Debian. > > The license begins with the permission grant: > > Permission is hereby granted, free of charge, to any person or > organization obtaining a copy of the software and accompanying > documentation covered by this license (the "Software") to use, > reproduce, display, distribute, execute, and transmit the > Software, and to prepare derivative works of the Software, and to > permit third-parties to whom the Software is furnished to do so, > all subject to the following: > > [... a restriction and a disclaimer paragraph ...] > > As I read this, "the Software" means "the unmodified tar or zip > file obtained from boost.org". Is that correct? No, it means whatever software says the licence applies to it. This licence does not (yet) apply to all of Boost. All parts of it are supposed to come with a licence that meets certain requirements, listed at <http://www.boost.org/more/lib_guide.htm#License>. The licence you are reading is supposed to be a standard licence that meets these requirements. There is a fuller explanation at <http://www.boost-consulting.com/boost/more/license_info.html>. > I'm permitted to "prepare derivative works of the Software", but the > license doesn't specify what I may do with my derivative works. > > Clearly, I may distribute "the Software", but may I distribute > the derivative work? I think that may be legally implicit, but I am not a lawyer. > Some licenses (e.g. the BSD and the GPL) make it clear that the terms > apply to both the software and to derivative works. Shouldn't the > boost license do likewise? Even if it is legally implicit, I can see that it would be a good idea to clarify it. Since it doesn't specify have a choice-of-law clause it could be interpreted according to any country's contract law and things that are implicit according to US law might not be so elsewhere. Ben.

1 0

compiling as a framework
by Avram Aelony 27 Oct '03

27 Oct '03

This may be a naive question, but on Mac Os X one can compile other libraries as a "framework", for example I can use the OpenGL library by compiling as follows: % g++ mytest.cpp -framework OpenGL Is it possible to be able to do the same style compilation for Boost? Ideally, something like this would be nice... % g++ mytest.cpp -framework Boost Incidentally, although I have installed Boost with bjam, simply compiling a Hello World style program that uses a Boost function gives me errors... An example would be great. thanks, Avram

1 0

directory_iterator TypeLoadException
by Sergey K. 26 Oct '03

26 Oct '03

Hello, I tried to run SimpleLs program, but got a TypeLoadException at the line below. I use boost-1.30.2, MSVC++7.0 Any idea what could be causing the problem? for ( fs::directory_iterator dir_itr( full_path ); dir_itr != end_iter; ++dir_itr ) // exception thrown here Output: In directory: C:\src\cpp Unhandled Exception: System.TypeLoadException: Could not load type boost.filesystem.dir_itr_imp from assembly Filesystem Demo, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null. at boost.==(shared_ptr<boost::filesystem::directory_iterator::dir_itr_imp>* a, shared_ptr<boost::filesystem::director y_iterator::dir_itr_imp>* b) at boost.filesystem.!=(directory_iterator* x, directory_iterator* y) in c:\lib\cpp\boost-1.30.2\boost\filesystem\oper ations.hpp:line 93 at main(Int32 argc, SByte** argv) in c:\src\cpp\boost\filesystemdemo\simplels.cpp:line 44

1 1

Interval Library on MIPS
by David A. Greene 26 Oct '03

26 Oct '03

Hi, I've been attempting to use the interval library on a MIPS/IRIX machine without luck. The problem is that there is no native rounding support and we don't have a C99 environment. I'm getting "Please specify rounding control mechanism" errors from the preprocessor. The thing is, I don't need a rounding mode. I simply want to use intervals of type int. I could understand the error if I was trying to use floating-point intervals but shouldn't I be able to specify intervals that don't require rounding? Or even specify intervals with a policy that ignores rounding? Has anyone run into this problem before? Is there a workaround? -Dave

2 1

MS C++ 7.1 warning C4244 (spirit)
by GIE 24 Oct '03

24 Oct '03

Hello! Is there any way to avoid this warning? =========Beginning of the citation============== ------ Build started: Project: [...], Configuration: Debug Win32 ------ Compiling... [...].cpp BOOST_DIR\boost\spirit\core\primitives\impl\pri mitives.ipp(62) : warning C4244: 'initializing' : conversion from '__w64 int' to 'int', possible loss of data BOOST_DIR\boost\spirit\core\primitives\primitiv es.hpp(190) : see reference to function template instantiation 'RT boost::spirit::impl::string_parser_parse<result_t,boost::unwrap_reference<T> ::type,const ScannerT>(IteratorT,IteratorT,const ScannerT &)' being compiled with [ RT=result_t, T=const char *, ScannerT=boost::spirit::scanner<std::basic_string<char,std::char_traits<char ,std::allocator<char>>::iterator,boost::spirit::scanner_policies<boost::spi rit::no_skipper_iteration_policy<boost::spirit::scanner_policies<boost::spir it::iter_policy_t>::iteration_policy_t>,boost::spirit::scanner_policies<boos t::spirit::iter_policy_t>::match_policy_t,boost::spirit::scanner_policies<bo ost::spirit::iter_policy_t>::action_policy_t>>, IteratorT=boost::unwrap_reference<const char *>::type ] [...] Linking... Build Time 0:04 Build log was saved at "file://PROJECT_DIR\Debug\BuildLog.htm" [...] - 0 error(s), 1 warning(s) ---------------------- Done ---------------------- Build: 1 succeeded, 0 failed, 0 skipped =========The end of the citation================ -- With best regards, GIE.

4 3

Can't build or install
by James Buchanan 24 Oct '03

24 Oct '03

I managed to run bjam -sTOOLS=mingw, and it seemed to do something for 10 minutes or so, but that was it. I found some of the libraries, such as the Regex project's libraries in the debug and release folders in static and dynamic link form, but other libraries didn't seem to build. Where are they, and how do I install the libraries in my library directory? I'd like all libraries except the Python libraries installed. Many thanks for your help, James

1 0

Re: [OT a bit] Condition variable and const-correctness
by Weston Markham 23 Oct '03

23 Oct '03

This might actually be slightly less off topic than the previous post, because it parallels the way that I think about that condition::wait method... Anyway, I'm curious what people think about: void perverse_strcpy( const char *src, char *dest, const char *done // note const ) { while (!done) { // note we expect change *dest++ = *src++; } } The caller can do something like: src = "hello world"; dest[strlen(src)] = 1; // store a nonzero value perverse_strcpy(src, dest, dest+strlen(src)); Yes, its a kinda stupid and, well, dubious function. However, the point is that "const char *" simply means that the pointer points to a char that can only be accessed as a "const char" through that pointer. It does not imply that the referenced thing is physically const. Nor does it imply that the referenced thing is logically const. (meaning that non-const methods can still be called on an object that has a "const Foo *" pointing to it; they simply can't be called through that pointer.) Does this run counter to what people believe the semantics of "const char *" to be? Are compilers permitted to optimize out the check of "!done" based on const-ness? (IIRC, they actually may in some related examples, if "src" and "dest" are types that should not alias to "done"; but this is not the case here) Is there any undefined or implementation-defined behavior of the above code? As separate aside, I believe that "physically const" refers specifically to a property of an object, say, the string constant "x". It is the reason why: const_cast<char*>("x")[0] = 'y' ... results in undefined behavior. The const keyword _could_ be used on an interface to indicate that a method will not produce undefined behavior when invoked on an instance that is actually physically const. This is different from using the const keyword to identify methods which maintain "logical constness". The latter meaning (whatever that may be) is what I believe is used in practice. (and the language is, I believe, designed to support this other meaning) Of course, I'm not, in some cases, sure what that meaning is! I suspect, by the way, that different people may have different ideas of how the const keyword should be applied to interfaces in practice. Each person might have an internally consistent viewpoint, but there may still be several mutually incompatible views. (I'm pretty sure that there are at least a few. I hope they are not as "notoriously arbitrary" :) as naming conventions!) Lastly, just because it amuses me: C++ Shrink: How does that const Foo * make you feel? Programmer: I feel frustrated, doc! I want to change things, but I can't. I know that the other coders do things that I can't; I can see all the changes that they make! Why not me? C++ Shrink: Hmm. Interesting. Weston Markham

1 0

RE: [Boost-users] Re: Condition variable and const-correctness
by Weston Markham 22 Oct '03

22 Oct '03

Mark, (and group) I may not have explained myself clearly in my original message. Your example ThreadedQueue::bMessageAvaliable() const actually demonstrates _exactly_ why I feel that condition::wait should be const. Your method modifies something internally (a boost::mutex; I have no argument whatsoever with the view that locking a mutex changes its state). Then it does some other things that don't affect its const-ness. Then it undoes the modifications it originally made. (By unlocking the mutex) A caller of this function should not care that these things go on internally. In this sense, it is logically const. I would also add that the caller of the function does not care that the precise behavior (say, when it returns, or in other examples, the exact value that it does) of the function can depend on the actions of other threads; this is the point that I had expected resistance on.) Similarly, the condition::wait will modify a mutex (unlocking it, and yes, through a non-const Lock object). It will do some other stuff. Bookkeeping or whatever, maybe even blocking itself. No matter what it does internally, by the time it returns control to its caller, all of this has been undone. The thread is not blocked. It is not in a waiting queue. The mutex that we pointed it at has been locked again. From the caller's perspective, the only things different after the call are: 1. Time has passed. 2. Some other threads have done some things that they might not have done otherwise. What they do is their own business. I don't see how that can affect this function's const-ness. (Am I missing something _here_?) My conclusion is that condition::wait is logically const. I will certainly admit that const-ness may be in the eye of the beholder. I expect that the physically const vs. logically const is a problem with some people. However, there do seem to be other examples of functions that are const (in their signatures) in the same spirit that my intuition tells me condition::wait is. Does this elucidate my position? Weston Markham Mark Sizer wrote: The condition wait() requires a lock, which requires a mutex. The mutex state is toggled from acquired to free to acquired whilst the wait() is waiting. It's the same problem that having a lock creates on a method such as this one: ThreadedQueue::bMessageAvailable() const { { boost::mutex::scoped_lock( _mutexQueue ) return !_queue.empty(); } } The only way to make that work is to declare the _mutexQueue as "mutable". In the case above, I agree with you: In terms of logical "const-ness", these methods are (or can be) const. In terms of physical "const-ness", they are not. Solve the problem with "mutable". However, the condition case is a bit more subtle. ThreadedQueue::messageNext() const { { boost::mutex::scoped_lock lockQueue( _mutexQueue ); if ( _queueOut.empty() ) { // (the lock is released before blocking, // then re-locked before continuing) _conditionMessageReady.wait( lockQueue ); } // get a message } } Is that really const? if the _mutexQueue and _conditionMessageReady are made "mutable" we can MAKE the method const (as shown), but is it? I'd say there is a EXPLICIT state change in the object: Into the waiting state. This is a change, therefore non-const. In the bMessageAvailable() case, there is no explicit state change, you're returning the existing state of the object. There is an implicit state change required to safely do so, which we've decided to hide. The only way this can block forever is bad coding - deadlock. When using a condition.wait(), you are making 2 big state changes: Both the object and the thread involved go from a "running" state into a "blocked" state, perhaps forever if nothing notifies (which is reasonable if the event never occurrs, not a coding deadlock error). That doesn't seem "const" to me. - Mark

4 6

smart_ptr without memory allocation
by John Aughey 22 Oct '03

22 Oct '03

I have a class that implements a buffer pool that allocates block of memory, and the users "free" the memory when it is no longer needed back to the buffer pool. Future allocations simply return the front of the free list. Simple enough, and the class returns shared_array<T> objects to automatically free the memory back into the proper buffer pool. The problem is, this mechanism is used so that during real-time operation (this is a real-time system), there is absolutely no memory allocations required. However, inside shared_array, it uses detail::shared_count and inside shared_count it performs a new to create a sp_counted_base object. So for every smart pointer object that supplies a deleter, it must perform a new. My proposal would be to include another constructor to both shared_array (and probably it's corresponding smart pointer brothers) and to shared_count that looks like: shared_array(T *p, sp_counted_base *d) : px(p), pn(d) { } shared_count(sp_counted_base *d) : pi_(d) { } (I haven't implemented this yet, so the above may not be quite right) The purpose of this is to supply an sp_counted_base object to the shared_* object that does the delete functionality. This eliminates the new in the case where a sp_counted_base object can be supplied. In the case of the managed buffer pool mentioned above, the sp_counted_base object could be allocated with the corresponding buffer, and then re-used for subsequent "allocations" from the free list. This should result in no dynamic allocations to create a shared_* object with a corresponding deleter. I hope this makes sense. It should only require two new constuctors. John

2 1

Bind causing crashes with VS.Net 7.1
by Mark Loew 22 Oct '03

22 Oct '03

I am using bind heavily in my application. I noticed a problem that may/may not be a boost issue but wanted to check if anyone had any quick insights. I am using 2 and 3 paramater functions with bind over a range with the for_each operator. What I have noticed is everything is fine when the system is build in debug mode. I then rebuild in release modes with all optimizations turned on. The boost code crashes with access violations. I disabled the optimization of Whole Program Optimization and everything is fine. I believe I have noticed this with other template functions where the whole program optimization causes problems. Has anyone seen this before and do you know what causes it? Just checking if this is a known boost problem or a VC 7.1 issues. Mark Loew, MCSD, MCSE Application Development Consultant Sagestone Consulting www.sagestone.com <http://www.sagestone.com/> Grand Rapids, MI 616-954-9556 x149 Microsoft Gold Certified Partner mloew(a)sagestone.com

2 1

enable_shared_from_this and inheritance
by sashan 22 Oct '03

22 Oct '03

I'm trying to use enable_shared_from_this with my classes that have an inheritance structure and a virtual function. I'd like to get a shared pointer to the descendant class B. I've attached 2 files. One compiles but errors at runtime, the other doesn;t compile. The first method uses makes both class A and B inherit from enable_shared_from_this. The 2nd method makes only the base class A inherit from enable_shared_from_this and tries to dynamic cast to shared_ptr. -- sashan http://www.cs.auckland.ac.nz/~sgov008/ #include <iostream> #include <boost/enable_shared_from_this.hpp> using namespace std; using namespace boost; class A : public enable_shared_from_this<A> { public: A(){ cout << "A" << endl; } virtual void f() { shared_ptr<A> pA(shared_from_this());} }; class B : public A, public enable_shared_from_this { public: B() { cout << "B" << endl;} virtual void f() { shared_ptr pB(enable_shared_from_this::shared_from_this()); } }; void main() { shared_ptr<A> a(new A); a->f(); shared_ptr b(new B); b->f(); } #include <iostream> #include <boost/enable_shared_from_this.hpp> using namespace std; using namespace boost; class A : public enable_shared_from_this<A> { public: A(){ cout << "A" << endl; } virtual void f() { shared_ptr<A> pA(shared_from_this());} }; class B : public A { public: B() { cout << "B" << endl;} virtual void f() { shared_ptr<A> pA(shared_from_this()); shared_ptr pB(dynamic_pointer_cast< shared_ptr >(pA)); } }; void main() { shared_ptr<A> a(new A); a->f(); shared_ptr b(new B); b->f(); }

2 2

which variant code should I use?
by Tom 22 Oct '03

22 Oct '03

It appears that there is a new variant library (boost::variant), but that it has been delayed. Also, there is the old boost.any library. And CUJ has a simple, ref-counted one here http://www.cuj.com/documents/s=8034/cuj0010cacciola/cacciola.htm. Also, CUJ has an article about boost::dynamic_any. Which should I use? I want to use one of the boost libraries, but I would like something small - meaning it won't addmuch to the size of my executable. Most boost libraries I can't use because they are too big (due to dependencies I assume). Thanks, Tom.

2 3

code bloat?
by Marton Fabo 22 Oct '03

22 Oct '03

Hi! I have looked around in the documentation and FAQs about my question, but I don't seem to have found a satisfying answer. My problem is that the boost libraries (especially function) seem to successfully boost the code size of my C++ Builder program, too. The source written by me is around twenty-some thousands of lines, plus the VCL and stdc++ headres, the end result may be somewhere around half a million lines in summary. But after having added some boost headers (mainly function and bind) to where it's appropriate, the amount of compiled lines on a full rebuild jumped to the ten million (!) range. This is way too much. I'm not using any so that much advanced stuff that it would be justified - and the compilation time is inacceptable for such a small app. So, does anyone have some clues regarding why boost may cause so much bloat, and how I could reduce that? thx mortee

5 8

enable_shared_from_this
by sashan 22 Oct '03

22 Oct '03

I'm trying to use enable_shared_from_this with my classes that have an inheritance structure and a virtual function. I'd like to get a shared pointer to the descendant class B. I get a compile error when I try to dynamic cast the shared ptr of type A to a shared_ptr of type B. See the attached sample. -- sashan http://www.cs.auckland.ac.nz/~sgov008/ #include <iostream> #include <boost/enable_shared_from_this.hpp> using namespace std; using namespace boost; class A : public enable_shared_from_this<A> { public: A(){ cout << "A" << endl; } virtual void f() =0; }; class B : public A { public: B() { cout << "B" << endl;} virtual void f() { shared_ptr<A> pA(enable_shared_from_this<A>::shared_from_this()); shared_ptr pB1(dynamic_pointer_cast < shared_ptr >(pA)); } }; void main() { B b; b.f(); }

1 1

Linking STLPort 4.3 and Boost with VC7.0
by Ray 21 Oct '03

21 Oct '03

How do i get theese three things to work together nicely? I cannot find any help for this (and i know it had to be asked before). //#include <iostream> #include <boost\spirit.hpp> int main () { boost::spirit::rule<> p = *(boost::spirit::real_p); return 0; } I get linker errors if i uncomment the iostream include STL Port is built to use its own streams. Works fine in other examples not using boost. I looked through the boost user config but didnt see anything relavant to throw boost a bone that im using STL Port. Any help would greatly be appreciated! Ray Hilton

3 6

new to Boost - need help with installation issues
by Avram Aelony 21 Oct '03

21 Oct '03

Hi, I would like to use Boost on my Powerbook G4 running Jaguar (Mac Os X 10.2.8). I have tried to make as much sense as possible from Boost documentation concerning bjam and tried to install Boost yet I suspect it failed, as I see no newly created target (library, object file, etc..). If anyone uses Boost running on Mac Os X, I would be grateful to learn of how they installed Boost and how they currently use Boost in the sense of "Best practices". I'm fluent in c++ and I look forward to being able to write my c++ code invoking Boost objects/functions. Any help appreciated. thanks, Avram More detailed info... Using my Powerbook G4 running Mac Os X 10.2.8 with gcc 3.3 and I did the following: -downloaded boost-1.30.2.tar.gz -downloaded boost-jam-3.1.7.tgz -created a directory in ~/Library called Boost and moved the two downloaded files there. -expanded downloaded boost-jam-3.1.7.tgz and ran build.sh -opened my ~/.cshrc file and set my path to include ~/Library/Boost/boost-jam-3.1.7/bin.macosxppc -expanded boost-1.30.2.tar.gz and went to directory with jam files -set up my environment variables relating to Python, i.e. setenv PYTHON_ROOT /sw/bin/python setenv PYTHON_LIB_PATH /sw/lib/python2.2/config setenv PYTHON_INCLUDES /sw/include/python2.2 [aa:~/Library/Boost/boost-1.30.2] aelony% which python /sw/bin/python [aa:~/Library/Boost/boost-1.30.2] aelony% python -V Python 2.2.2 -ran bjam [aa:~] aelony% which bjam /Users/aelony/Library/Boost/boost-jam-3.1.7/bin.macosxppc/bjam [aa:~] aelony% cd /Users/aelony/Library/Boost/boost-1.30.2 [aa:~/Library/Boost/boost-1.30.2] aelony% ls Jamfile* boost/ doc/ more/ tools/ Jamfile.v2* boost-build.jam* google_logo_40wht.gif* people/ Jamrules* boost.css* index.htm* project-root.jam* README* c++boost.gif* libs/ status/ Here is what it output, with modest indications of failure.... [aa:~/Library/Boost/boost-1.30.2] aelony% bjam ...patience... ...found 3066 targets... ...updating 138 targets... MkDir1 libs/python/build/bin-stage MkDir1 libs/python/build/bin MkDir1 libs/python/build/bin/libboost_python.dylib MkDir1 libs/python/build/bin/libboost_python.dylib/gcc MkDir1 libs/python/build/bin/libboost_python.dylib/gcc/debug MkDir1 libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic MkDir1 libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/numeric.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/tuple.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/numeric.hpp:9, from libs/python/src/numeric.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/list.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/list.hpp:9, from libs/python/src/list.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/long.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/long.hpp:9, from libs/python/src/long.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/dict.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/dict.hpp:9, from libs/python/src/dict.cpp:1: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/tuple.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/tuple.hpp:9, from libs/python/src/tuple.cpp:1: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/str.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/str.hpp:9, from libs/python/src/str.cpp:1: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/aix_init_module.o gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/from_python.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ rvalue_from_python_data.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ from_python.hpp:11, from libs/python/src/converter/from_python.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/registry.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ rvalue_from_python_data.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ registry.hpp:12, from libs/python/src/converter/registry.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/type_id.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_class.hpp:21, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ indirect_traits.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ decorated_type_id.hpp:10, from libs/python/src/converter/type_id.cpp:8: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/enum.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ enum_base.hpp:9, from libs/python/src/object/enum.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/class.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ class.hpp:13, from libs/python/src/object/class.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/function.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/handle.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/args_fwd.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ function.hpp:10, from libs/python/src/object/function.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/inheritance.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ inheritance.hpp:12, from libs/python/src/object/inheritance.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/life_support.o gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/pickle_support.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ rvalue_from_python_data.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ registry.hpp:12, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_value.hpp:12, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ default_call_policies.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ make_function.hpp:9, from libs/python/src/object/pickle_support.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/errors.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from libs/python/src/errors.cpp:11: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) In file included from libs/python/src/errors.cpp:12: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178:23: warning: integer constant is so large that it is unsigned In file included from libs/python/src/errors.cpp:12: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178: warning: this decimal constant is unsigned only in ISO C90 gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/module.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/scope.hpp:9, from libs/python/src/module.cpp:9: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/builtin_converters.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/handle.hpp:11, from libs/python/src/converter/builtin_converters.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) In file included from libs/python/src/converter/builtin_converters.cpp:21: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178:23: warning: integer constant is so large that it is unsigned In file included from libs/python/src/converter/builtin_converters.cpp:21: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178: warning: this decimal constant is unsigned only in ISO C90 gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/arg_to_python_base.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/handle.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python_base.hpp:9, from libs/python/src/converter/arg_to_python_base.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/iterator.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:29, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function2.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ function_object.hpp:9, from libs/python/src/object/iterator.cpp:8: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/object_protocol.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_protocol.hpp:12, from libs/python/src/object_protocol.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/object_operators.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_operators.hpp:9, from libs/python/src/object_operators.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-Link-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_python_debug.dylib c++: unrecognized option `-shared' ld: Undefined symbols: _main _PyCallable_Check _PyErr_Clear _PyErr_Format _PyEval_CallFunction _PyExc_ImportError _PyImport_Import _PyInt_FromLong _PyObject_GetAttrString _PyObject_IsInstance _PyString_FromStringAndSize _PyType_IsSubtype _PyType_Type _PyErr_Occurred _PyInt_AsLong _PyList_Append _PyList_Insert _PyList_New _PyList_Reverse _PyList_Sort _PyList_Type _PyObject_CallFunction _PyLong_Type _PyDict_Clear _PyDict_Copy _PyDict_GetItem _PyDict_Items _PyDict_Keys _PyDict_New _PyDict_Type _PyDict_Update _PyDict_Values __Py_NoneStruct _PyTuple_New _PyTuple_Type _PyObject_CallMethod _PyString_FromString _PyString_Type _PyErr_SetObject _PyExc_ReferenceError _PyExc_TypeError _PyString_FromFormat _PyInt_Type _PyLong_FromUnsignedLong _PyObject_IsTrue _PyObject_RichCompareBool _PyObject_Size _PyString_AsString _PyType_Ready _PyBaseObject_Type _PyCFunction_New _PyErr_SetString _PyExc_RuntimeError _PyMem_Free _PyMem_Malloc _PyModule_Type _PyObject_ClearWeakRefs _PyObject_SetAttrString _PyProperty_Type _PyStaticMethod_New _PyType_GenericAlloc _PyClass_Type _PyDict_Size _PyErr_BadArgument _PyMethod_New _PyObject_GetItem _PyObject_SetAttr _PyStaticMethod_Type _PyString_InternFromString _PyTuple_Size __Py_NotImplementedStruct _PyWeakref_NewRef __PyObject_New _PyComplex_Type _PyErr_NoMemory _PyExc_OverflowError _Py_InitModule4 _PyComplex_ImagAsDouble _PyComplex_RealAsDouble _PyFloat_Type _PyLong_AsLongLong _PyLong_AsUnsignedLong _PyLong_AsUnsignedLongLong _PyString_Size _PyExc_StopIteration _PyErr_ExceptionMatches _PyExc_AttributeError _PyObject_DelItem _PyObject_GetAttr _PyObject_SetItem _PySequence_DelSlice _PySequence_GetSlice _PySequence_SetSlice _PySlice_New __PyEval_SliceIndex _PyNumber_Add _PyNumber_And _PyNumber_Divide _PyNumber_InPlaceAdd _PyNumber_InPlaceAnd _PyNumber_InPlaceDivide _PyNumber_InPlaceLshift _PyNumber_InPlaceMultiply _PyNumber_InPlaceOr _PyNumber_InPlaceRemainder _PyNumber_InPlaceRshift _PyNumber_InPlaceSubtract _PyNumber_InPlaceXor _PyNumber_Lshift _PyNumber_Multiply _PyNumber_Or _PyNumber_Remainder _PyNumber_Rshift _PyNumber_Subtract _PyNumber_Xor DYLD_LIBRARY_PATH=/sw/lib/python2.2/config export DYLD_LIBRARY_PATH c++ -g -fPIC -shared -o "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_python_debug.dylib" -L"/sw/lib/python2.2/config" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/numeric.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/list.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/long.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/dict.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/tuple.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/str.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/aix_init_module.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/from_python.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/registry.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/type_id.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/enum.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/class.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/function.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/inheritance.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/life_support.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/pickle_support.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/errors.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/module.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/builtin_converters.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/arg_to_python_base.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/iterator.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/object_protocol.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/object_operators.o" ...failed gcc-Link-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_python_debug.dylib... ...skipped <!libs!python!build!bin-stage>libboost_python_debug.dylib for lack of <libs!python!build/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true>libboost_python_debug.dylib... MkDir1 libs/python/build/bin/libboost_python.dylib/gcc/release MkDir1 libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic MkDir1 libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/numeric.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/tuple.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/numeric.hpp:9, from libs/python/src/numeric.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/list.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/list.hpp:9, from libs/python/src/list.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/long.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/long.hpp:9, from libs/python/src/long.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/dict.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/dict.hpp:9, from libs/python/src/dict.cpp:1: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/tuple.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/tuple.hpp:9, from libs/python/src/tuple.cpp:1: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/str.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/str.hpp:9, from libs/python/src/str.cpp:1: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/aix_init_module.o gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/from_python.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ rvalue_from_python_data.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ from_python.hpp:11, from libs/python/src/converter/from_python.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/registry.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ rvalue_from_python_data.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ registry.hpp:12, from libs/python/src/converter/registry.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/type_id.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_class.hpp:21, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ indirect_traits.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ decorated_type_id.hpp:10, from libs/python/src/converter/type_id.cpp:8: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/enum.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ enum_base.hpp:9, from libs/python/src/object/enum.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/class.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ class.hpp:13, from libs/python/src/object/class.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/function.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/handle.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/args_fwd.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ function.hpp:10, from libs/python/src/object/function.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/inheritance.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ inheritance.hpp:12, from libs/python/src/object/inheritance.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) libs/python/src/object/inheritance.cpp: In function ` __gnu_cxx::__normal_iterator<boost::<unnamed>::index_entry*, std::vector<boost::<unnamed>::index_entry, std::allocator<boost::<unnamed>::index_entry> > > boost::<unnamed>::demand_type(boost::python::type_info)': libs/python/src/object/inheritance.cpp:217: warning: unused variable `vertex_t v2' gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/life_support.o gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/pickle_support.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ rvalue_from_python_data.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ registry.hpp:12, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_value.hpp:12, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ default_call_policies.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ make_function.hpp:9, from libs/python/src/object/pickle_support.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/errors.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from libs/python/src/errors.cpp:11: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) In file included from libs/python/src/errors.cpp:12: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178:23: warning: integer constant is so large that it is unsigned In file included from libs/python/src/errors.cpp:12: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178: warning: this decimal constant is unsigned only in ISO C90 gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/module.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/scope.hpp:9, from libs/python/src/module.cpp:9: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/builtin_converters.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/handle.hpp:11, from libs/python/src/converter/builtin_converters.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) In file included from libs/python/src/converter/builtin_converters.cpp:21: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178:23: warning: integer constant is so large that it is unsigned In file included from libs/python/src/converter/builtin_converters.cpp:21: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178: warning: this decimal constant is unsigned only in ISO C90 gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/arg_to_python_base.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/handle.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python_base.hpp:9, from libs/python/src/converter/arg_to_python_base.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/iterator.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:29, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function2.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ function_object.hpp:9, from libs/python/src/object/iterator.cpp:8: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/object_protocol.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_protocol.hpp:12, from libs/python/src/object_protocol.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/object_operators.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_operators.hpp:9, from libs/python/src/object_operators.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-Link-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/libboost_python.dylib c++: unrecognized option `-shared' ld: Undefined symbols: _main _PyCallable_Check _PyErr_Clear _PyErr_Format _PyEval_CallFunction _PyExc_ImportError _PyImport_Import _PyInt_FromLong _PyObject_GetAttrString _PyObject_IsInstance _PyString_FromStringAndSize _PyType_IsSubtype _PyType_Type _PyErr_Occurred _PyInt_AsLong _PyList_Append _PyList_Insert _PyList_New _PyList_Reverse _PyList_Sort _PyList_Type _PyObject_CallFunction _PyLong_Type _PyDict_Clear _PyDict_Copy _PyDict_GetItem _PyDict_Items _PyDict_Keys _PyDict_New _PyDict_Type _PyDict_Update _PyDict_Values __Py_NoneStruct _PyTuple_New _PyTuple_Type _PyObject_CallMethod _PyString_FromString _PyString_Type _PyErr_SetObject _PyExc_ReferenceError _PyExc_TypeError _PyString_FromFormat _PyInt_Type _PyLong_FromUnsignedLong _PyObject_IsTrue _PyObject_RichCompareBool _PyObject_Size _PyString_AsString _PyType_Ready _PyBaseObject_Type _PyCFunction_New _PyErr_SetString _PyExc_RuntimeError _PyMem_Free _PyMem_Malloc _PyModule_Type _PyObject_ClearWeakRefs _PyObject_SetAttrString _PyProperty_Type _PyStaticMethod_New _PyType_GenericAlloc _PyClass_Type _PyDict_Size _PyErr_BadArgument _PyMethod_New _PyObject_GetItem _PyObject_SetAttr _PyStaticMethod_Type _PyString_InternFromString _PyTuple_Size __Py_NotImplementedStruct _PyWeakref_NewRef __PyObject_New _PyComplex_Type _PyErr_NoMemory _PyExc_OverflowError _Py_InitModule4 _PyComplex_ImagAsDouble _PyComplex_RealAsDouble _PyFloat_Type _PyLong_AsLongLong _PyLong_AsUnsignedLong _PyLong_AsUnsignedLongLong _PyString_Size _PyExc_StopIteration _PyErr_ExceptionMatches _PyExc_AttributeError _PyObject_DelItem _PyObject_GetAttr _PyObject_SetItem _PySequence_DelSlice _PySequence_GetSlice _PySequence_SetSlice _PySlice_New __PyEval_SliceIndex _PyNumber_Add _PyNumber_And _PyNumber_Divide _PyNumber_InPlaceAdd _PyNumber_InPlaceAnd _PyNumber_InPlaceDivide _PyNumber_InPlaceLshift _PyNumber_InPlaceMultiply _PyNumber_InPlaceOr _PyNumber_InPlaceRemainder _PyNumber_InPlaceRshift _PyNumber_InPlaceSubtract _PyNumber_InPlaceXor _PyNumber_Lshift _PyNumber_Multiply _PyNumber_Or _PyNumber_Remainder _PyNumber_Rshift _PyNumber_Subtract _PyNumber_Xor DYLD_LIBRARY_PATH=/sw/lib/python2.2/config export DYLD_LIBRARY_PATH c++ -s -fPIC -shared -o "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/libboost_python.dylib" -L"/sw/lib/python2.2/config" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/numeric.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/list.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/long.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/dict.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/tuple.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/str.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/aix_init_module.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/from_python.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/registry.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/type_id.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/enum.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/class.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/function.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/inheritance.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/life_support.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/pickle_support.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/errors.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/module.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/builtin_converters.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/arg_to_python_base.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/iterator.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/object_protocol.o" "libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/object_operators.o" ...failed gcc-Link-action libs/python/build/bin/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/libboost_python.dylib... ...skipped <!libs!python!build!bin-stage>libboost_python.dylib for lack of <libs!python!build/libboost_python.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true>libboost_python.dylib... MkDir1 libs/python/build/bin/libboost_python.a MkDir1 libs/python/build/bin/libboost_python.a/gcc MkDir1 libs/python/build/bin/libboost_python.a/gcc/debug MkDir1 libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ numeric.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/tuple.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/numeric.hpp:9, from libs/python/src/numeric.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ list.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/list.hpp:9, from libs/python/src/list.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ long.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/long.hpp:9, from libs/python/src/long.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ dict.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/dict.hpp:9, from libs/python/src/dict.cpp:1: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ tuple.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/tuple.hpp:9, from libs/python/src/tuple.cpp:1: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ str.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/str.hpp:9, from libs/python/src/str.cpp:1: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ aix_init_module.o gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ from_python.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ rvalue_from_python_data.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ from_python.hpp:11, from libs/python/src/converter/from_python.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ registry.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ rvalue_from_python_data.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ registry.hpp:12, from libs/python/src/converter/registry.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ type_id.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_class.hpp:21, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ indirect_traits.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ decorated_type_id.hpp:10, from libs/python/src/converter/type_id.cpp:8: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ enum.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ enum_base.hpp:9, from libs/python/src/object/enum.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ class.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ class.hpp:13, from libs/python/src/object/class.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ function.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/handle.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/args_fwd.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ function.hpp:10, from libs/python/src/object/function.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ inheritance.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ inheritance.hpp:12, from libs/python/src/object/inheritance.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ life_support.o gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ pickle_support.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ rvalue_from_python_data.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ registry.hpp:12, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_value.hpp:12, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ default_call_policies.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ make_function.hpp:9, from libs/python/src/object/pickle_support.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ errors.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from libs/python/src/errors.cpp:11: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) In file included from libs/python/src/errors.cpp:12: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178:23: warning: integer constant is so large that it is unsigned In file included from libs/python/src/errors.cpp:12: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178: warning: this decimal constant is unsigned only in ISO C90 gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ module.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/scope.hpp:9, from libs/python/src/module.cpp:9: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ builtin_converters.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/handle.hpp:11, from libs/python/src/converter/builtin_converters.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) In file included from libs/python/src/converter/builtin_converters.cpp:21: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178:23: warning: integer constant is so large that it is unsigned In file included from libs/python/src/converter/builtin_converters.cpp:21: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178: warning: this decimal constant is unsigned only in ISO C90 gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ arg_to_python_base.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/handle.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python_base.hpp:9, from libs/python/src/converter/arg_to_python_base.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ iterator.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:29, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function2.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ function_object.hpp:9, from libs/python/src/object/iterator.cpp:8: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ object_protocol.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_protocol.hpp:12, from libs/python/src/object_protocol.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ object_operators.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_operators.hpp:9, from libs/python/src/object_operators.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-Archive-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ libboost_python_debug.a ar: creating archive libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ libboost_python_debug.a Ranlib libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ libboost_python_debug.a FileClone libs/python/build/bin-stage/libboost_python_debug.a MkDir1 libs/python/build/bin/libboost_python.a/gcc/release MkDir1 libs/python/build/bin/libboost_python.a/gcc/release/runtime-link-dynamic gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/numeric.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/tuple.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/numeric.hpp:9, from libs/python/src/numeric.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/list.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/list.hpp:9, from libs/python/src/list.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/long.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/long.hpp:9, from libs/python/src/long.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/dict.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/dict.hpp:9, from libs/python/src/dict.cpp:1: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/tuple.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/tuple.hpp:9, from libs/python/src/tuple.cpp:1: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/str.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/str.hpp:9, from libs/python/src/str.cpp:1: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/aix_init_module.o gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/from_python.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ rvalue_from_python_data.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ from_python.hpp:11, from libs/python/src/converter/from_python.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/registry.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ rvalue_from_python_data.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ registry.hpp:12, from libs/python/src/converter/registry.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/type_id.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_class.hpp:21, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ indirect_traits.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ decorated_type_id.hpp:10, from libs/python/src/converter/type_id.cpp:8: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) ...on 100th target... gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/enum.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ enum_base.hpp:9, from libs/python/src/object/enum.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/class.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ class.hpp:13, from libs/python/src/object/class.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/function.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/handle.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/args_fwd.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ function.hpp:10, from libs/python/src/object/function.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/inheritance.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ inheritance.hpp:12, from libs/python/src/object/inheritance.cpp:6: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) libs/python/src/object/inheritance.cpp: In function ` __gnu_cxx::__normal_iterator<boost::<unnamed>::index_entry*, std::vector<boost::<unnamed>::index_entry, std::allocator<boost::<unnamed>::index_entry> > > boost::<unnamed>::demand_type(boost::python::type_info)': libs/python/src/object/inheritance.cpp:217: warning: unused variable `vertex_t v2' gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/life_support.o gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/pickle_support.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ rvalue_from_python_data.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ registry.hpp:12, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_value.hpp:12, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ default_call_policies.hpp:10, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ make_function.hpp:9, from libs/python/src/object/pickle_support.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/python/detail/ referent_storage.hpp:32: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/errors.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from libs/python/src/errors.cpp:11: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) In file included from libs/python/src/errors.cpp:12: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178:23: warning: integer constant is so large that it is unsigned In file included from libs/python/src/errors.cpp:12: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178: warning: this decimal constant is unsigned only in ISO C90 gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/module.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/scope.hpp:9, from libs/python/src/module.cpp:9: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/builtin_converters.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/handle.hpp:11, from libs/python/src/converter/builtin_converters.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) In file included from libs/python/src/converter/builtin_converters.cpp:21: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178:23: warning: integer constant is so large that it is unsigned In file included from libs/python/src/converter/builtin_converters.cpp:21: /Users/aelony/Library/Boost/boost-1.30.2/boost/cast.hpp:178: warning: this decimal constant is unsigned only in ISO C90 gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/arg_to_python_base.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:19, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function0.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/errors.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/handle.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python_base.hpp:9, from libs/python/src/converter/arg_to_python_base.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/iterator.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ arithmetic_traits.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_base.hpp:25, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ prologue.hpp:22, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function_template.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/detail/ maybe_include.hpp:29, from /Users/aelony/Library/Boost/boost-1.30.2/boost/function/ function2.hpp:17, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/object/ function_object.hpp:9, from libs/python/src/object/iterator.cpp:8: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/object_protocol.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_protocol.hpp:12, from libs/python/src/object_protocol.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-C++-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/object_operators.o In file included from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_arithmetic.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_scalar.hpp:13, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_pod.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ has_trivial_assign.hpp:15, from /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ object_traits.hpp:18, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ to_python_indirect.hpp:9, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/converter/ arg_to_python.hpp:11, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/call.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_core.hpp:14, from /Users/aelony/Library/Boost/boost-1.30.2/boost/python/ object_operators.hpp:9, from libs/python/src/object_operators.cpp:7: /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: use of `long double' type; its size may change in a future release /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: (Long double usage is reported only once for each file. /Users/aelony/Library/Boost/boost-1.30.2/boost/type_traits/ is_float.hpp:22: warning: To disable this warning, use -Wno-long-double.) gcc-Archive-action libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/libboost_python.a ar: creating archive libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/libboost_python.a Ranlib libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/libboost_python.a ranlib: file: libs/python/build/bin/libboost_python.a/gcc/release/runtime-link- dynamic/libboost_python.a(aix_init_module.o) has no symbols FileClone libs/python/build/bin-stage/libboost_python.a gcc-Link-action libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_regex_debug.dylib c++: unrecognized option `-shared' ld: Undefined symbols: _main export DYLD_LIBRARY_PATH c++ -g -fPIC -shared -o "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_regex_debug.dylib" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/c_regex_traits.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/c_regex_traits_common.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/cpp_regex_traits.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/cregex.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/fileiter.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/posix_api.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/regex.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/regex_debug.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/regex_synch.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/w32_regex_traits.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/wide_posix_api.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/instances.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/winstances.o" ...failed gcc-Link-action libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_regex_debug.dylib... ...skipped <!libs!regex!build!bin-stage>libboost_regex_debug.dylib for lack of <libs!regex!build/libboost_regex.dylib/gcc/debug/runtime-link-dynamic/ shared-linkable-true>libboost_regex_debug.dylib... gcc-Link-action libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/libboost_regex.dylib c++: unrecognized option `-shared' ld: Undefined symbols: _main export DYLD_LIBRARY_PATH c++ -s -fPIC -shared -o "libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/libboost_regex.dylib" "libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/c_regex_traits.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/c_regex_traits_common.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/cpp_regex_traits.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/cregex.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/fileiter.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/posix_api.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/regex.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/regex_debug.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/regex_synch.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/w32_regex_traits.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/wide_posix_api.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/instances.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/winstances.o" ...failed gcc-Link-action libs/regex/build/bin/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/libboost_regex.dylib... ...skipped <!libs!regex!build!bin-stage>libboost_regex.dylib for lack of <libs!regex!build/libboost_regex.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true>libboost_regex.dylib... gcc-Link-action libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_threadd.dylib c++: unrecognized option `-shared' ld: Undefined symbols: _main export DYLD_LIBRARY_PATH c++ -g -fPIC -shared -o "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_threadd.dylib" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/condition.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/mutex.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/recursive_mutex.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/thread.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/tss.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/xtime.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/once.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/exceptions.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/threadmon.o" ...failed gcc-Link-action libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_threadd.dylib... ...skipped <!libs!thread!build!bin-stage>libboost_threadd.dylib for lack of <libs!thread!build/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true>libboost_threadd.dylib... gcc-Link-action libs/thread/build/bin/libboost_thread.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/libboost_thread.dylib c++: unrecognized option `-shared' ld: Undefined symbols: _main export DYLD_LIBRARY_PATH c++ -s -fPIC -shared -o "libs/thread/build/bin/libboost_thread.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/libboost_thread.dylib" "libs/thread/build/bin/libboost_thread.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/condition.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/mutex.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/recursive_mutex.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/thread.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/tss.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/xtime.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/once.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/exceptions.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/threadmon.o" ...failed gcc-Link-action libs/thread/build/bin/libboost_thread.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/libboost_thread.dylib... ...skipped <!libs!thread!build!bin-stage>libboost_thread.dylib for lack of <libs!thread!build/libboost_thread.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true>libboost_thread.dylib... gcc-Archive-action libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ libboost_python.a ar: creating archive libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ libboost_python.a Ranlib libs/python/build/bin/libboost_python.a/gcc/debug/runtime-link-dynamic/ libboost_python.a gcc-Link-action libs/date_time/build/bin/libboost_date_time.dylib/gcc/debug/runtime- link-dynamic/shared-linkable-true/libboost_date_time.dylib c++: unrecognized option `-shared' ld: Undefined symbols: _main export DYLD_LIBRARY_PATH c++ -g -fPIC -shared -o "libs/date_time/build/bin/libboost_date_time.dylib/gcc/debug/runtime- link-dynamic/shared-linkable-true/libboost_date_time.dylib" "libs/date_time/build/bin/libboost_date_time.dylib/gcc/debug/runtime- link-dynamic/shared-linkable-true/greg_month.o" "libs/date_time/build/bin/libboost_date_time.dylib/gcc/debug/runtime- link-dynamic/shared-linkable-true/greg_weekday.o" ...failed gcc-Link-action libs/date_time/build/bin/libboost_date_time.dylib/gcc/debug/runtime- link-dynamic/shared-linkable-true/libboost_date_time.dylib... gcc-Link-action libs/date_time/build/bin/libboost_date_time.dylib/gcc/release/runtime- link-dynamic/shared-linkable-true/libboost_date_time.dylib c++: unrecognized option `-shared' ld: Undefined symbols: _main export DYLD_LIBRARY_PATH c++ -s -fPIC -shared -o "libs/date_time/build/bin/libboost_date_time.dylib/gcc/release/runtime- link-dynamic/shared-linkable-true/libboost_date_time.dylib" "libs/date_time/build/bin/libboost_date_time.dylib/gcc/release/runtime- link-dynamic/shared-linkable-true/greg_month.o" "libs/date_time/build/bin/libboost_date_time.dylib/gcc/release/runtime- link-dynamic/shared-linkable-true/greg_weekday.o" ...failed gcc-Link-action libs/date_time/build/bin/libboost_date_time.dylib/gcc/release/runtime- link-dynamic/shared-linkable-true/libboost_date_time.dylib... gcc-Link-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_python.dylib c++: unrecognized option `-shared' ld: Undefined symbols: _main _PyCallable_Check _PyErr_Clear _PyErr_Format _PyEval_CallFunction _PyExc_ImportError _PyImport_Import _PyInt_FromLong _PyObject_GetAttrString _PyObject_IsInstance _PyString_FromStringAndSize _PyType_IsSubtype _PyType_Type _PyErr_Occurred _PyInt_AsLong _PyList_Append _PyList_Insert _PyList_New _PyList_Reverse _PyList_Sort _PyList_Type _PyObject_CallFunction _PyLong_Type _PyDict_Clear _PyDict_Copy _PyDict_GetItem _PyDict_Items _PyDict_Keys _PyDict_New _PyDict_Type _PyDict_Update _PyDict_Values __Py_NoneStruct _PyTuple_New _PyTuple_Type _PyObject_CallMethod _PyString_FromString _PyString_Type _PyErr_SetObject _PyExc_ReferenceError _PyExc_TypeError _PyString_FromFormat _PyInt_Type _PyLong_FromUnsignedLong _PyObject_IsTrue _PyObject_RichCompareBool _PyObject_Size _PyString_AsString _PyType_Ready _PyBaseObject_Type _PyCFunction_New _PyErr_SetString _PyExc_RuntimeError _PyMem_Free _PyMem_Malloc _PyModule_Type _PyObject_ClearWeakRefs _PyObject_SetAttrString _PyProperty_Type _PyStaticMethod_New _PyType_GenericAlloc _PyClass_Type _PyDict_Size _PyErr_BadArgument _PyMethod_New _PyObject_GetItem _PyObject_SetAttr _PyStaticMethod_Type _PyString_InternFromString _PyTuple_Size __Py_NotImplementedStruct _PyWeakref_NewRef __PyObject_New _PyComplex_Type _PyErr_NoMemory _PyExc_OverflowError _Py_InitModule4 _PyComplex_ImagAsDouble _PyComplex_RealAsDouble _PyFloat_Type _PyLong_AsLongLong _PyLong_AsUnsignedLong _PyLong_AsUnsignedLongLong _PyString_Size _PyExc_StopIteration _PyErr_ExceptionMatches _PyExc_AttributeError _PyObject_DelItem _PyObject_GetAttr _PyObject_SetItem _PySequence_DelSlice _PySequence_GetSlice _PySequence_SetSlice _PySlice_New __PyEval_SliceIndex _PyNumber_Add _PyNumber_And _PyNumber_Divide _PyNumber_InPlaceAdd _PyNumber_InPlaceAnd _PyNumber_InPlaceDivide _PyNumber_InPlaceLshift _PyNumber_InPlaceMultiply _PyNumber_InPlaceOr _PyNumber_InPlaceRemainder _PyNumber_InPlaceRshift _PyNumber_InPlaceSubtract _PyNumber_InPlaceXor _PyNumber_Lshift _PyNumber_Multiply _PyNumber_Or _PyNumber_Remainder _PyNumber_Rshift _PyNumber_Subtract _PyNumber_Xor DYLD_LIBRARY_PATH=/sw/lib/python2.2/config export DYLD_LIBRARY_PATH c++ -g -fPIC -shared -o "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_python.dylib" -L"/sw/lib/python2.2/config" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/numeric.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/list.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/long.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/dict.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/tuple.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/str.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/aix_init_module.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/from_python.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/registry.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/type_id.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/enum.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/class.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/function.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/inheritance.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/life_support.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/pickle_support.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/errors.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/module.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/builtin_converters.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/arg_to_python_base.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/iterator.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/object_protocol.o" "libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/object_operators.o" ...failed gcc-Link-action libs/python/build/bin/libboost_python.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_python.dylib... gcc-Link-action libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_regex.dylib c++: unrecognized option `-shared' ld: Undefined symbols: _main export DYLD_LIBRARY_PATH c++ -g -fPIC -shared -o "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_regex.dylib" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/c_regex_traits.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/c_regex_traits_common.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/cpp_regex_traits.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/cregex.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/fileiter.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/posix_api.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/regex.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/regex_debug.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/regex_synch.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/w32_regex_traits.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/wide_posix_api.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/instances.o" "libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/winstances.o" ...failed gcc-Link-action libs/regex/build/bin/libboost_regex.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_regex.dylib... gcc-Link-action libs/signals/build/bin/libboost_signals.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_signals.dylib c++: unrecognized option `-shared' ld: Undefined symbols: _main export DYLD_LIBRARY_PATH c++ -g -fPIC -shared -o "libs/signals/build/bin/libboost_signals.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_signals.dylib" "libs/signals/build/bin/libboost_signals.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/trackable.o" "libs/signals/build/bin/libboost_signals.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/connection.o" "libs/signals/build/bin/libboost_signals.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/signal_base.o" "libs/signals/build/bin/libboost_signals.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/slot.o" ...failed gcc-Link-action libs/signals/build/bin/libboost_signals.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_signals.dylib... gcc-Link-action libs/signals/build/bin/libboost_signals.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/libboost_signals.dylib c++: unrecognized option `-shared' ld: Undefined symbols: _main export DYLD_LIBRARY_PATH c++ -s -fPIC -shared -o "libs/signals/build/bin/libboost_signals.dylib/gcc/release/runtime- link-dynamic/shared-linkable-true/libboost_signals.dylib" "libs/signals/build/bin/libboost_signals.dylib/gcc/release/runtime- link-dynamic/shared-linkable-true/trackable.o" "libs/signals/build/bin/libboost_signals.dylib/gcc/release/runtime- link-dynamic/shared-linkable-true/connection.o" "libs/signals/build/bin/libboost_signals.dylib/gcc/release/runtime- link-dynamic/shared-linkable-true/signal_base.o" "libs/signals/build/bin/libboost_signals.dylib/gcc/release/runtime- link-dynamic/shared-linkable-true/slot.o" ...failed gcc-Link-action libs/signals/build/bin/libboost_signals.dylib/gcc/release/runtime-link- dynamic/shared-linkable-true/libboost_signals.dylib... gcc-Link-action libs/test/build/bin/libboost_prg_exec_monitor.dylib/gcc/debug/runtime- link-static/shared-linkable-true/libboost_prg_exec_monitor.dylib c++: unrecognized option `-shared' ld: can't locate file for: -lcrt0.o export DYLD_LIBRARY_PATH c++ -static -g -fPIC -shared -o "libs/test/build/bin/libboost_prg_exec_monitor.dylib/gcc/debug/runtime- link-static/shared-linkable-true/libboost_prg_exec_monitor.dylib" "libs/test/build/bin/libboost_prg_exec_monitor.dylib/gcc/debug/runtime- link-static/shared-linkable-true/execution_monitor.o" "libs/test/build/bin/libboost_prg_exec_monitor.dylib/gcc/debug/runtime- link-static/shared-linkable-true/cpp_main.o" ...failed gcc-Link-action libs/test/build/bin/libboost_prg_exec_monitor.dylib/gcc/debug/runtime- link-static/shared-linkable-true/libboost_prg_exec_monitor.dylib... gcc-Link-action libs/test/build/bin/libboost_prg_exec_monitor.dylib/gcc/debug/runtime- link-dynamic/shared-linkable-true/libboost_prg_exec_monitor.dylib c++: unrecognized option `-shared' ld: Undefined symbols: cpp_main(int, char**) export DYLD_LIBRARY_PATH c++ -g -fPIC -shared -o "libs/test/build/bin/libboost_prg_exec_monitor.dylib/gcc/debug/runtime- link-dynamic/shared-linkable-true/libboost_prg_exec_monitor.dylib" "libs/test/build/bin/libboost_prg_exec_monitor.dylib/gcc/debug/runtime- link-dynamic/shared-linkable-true/execution_monitor.o" "libs/test/build/bin/libboost_prg_exec_monitor.dylib/gcc/debug/runtime- link-dynamic/shared-linkable-true/cpp_main.o" ...failed gcc-Link-action libs/test/build/bin/libboost_prg_exec_monitor.dylib/gcc/debug/runtime- link-dynamic/shared-linkable-true/libboost_prg_exec_monitor.dylib... gcc-Link-action libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/runtime- link-static/shared-linkable-true/libboost_test_exec_monitor.dylib c++: unrecognized option `-shared' ld: can't locate file for: -lcrt0.o export DYLD_LIBRARY_PATH c++ -static -g -fPIC -shared -o "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/ libboost_test_exec_monitor.dylib" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/execution_monitor.o" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/test_tools.o" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/unit_test_parameters.o" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/unit_test_log.o" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/unit_test_monitor.o" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/unit_test_result.o" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/unit_test_suite.o" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/test_main.o" ...failed gcc-Link-action libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/runtime- link-static/shared-linkable-true/libboost_test_exec_monitor.dylib... gcc-Link-action libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/runtime- link-dynamic/shared-linkable-true/libboost_test_exec_monitor.dylib c++: unrecognized option `-shared' ld: Undefined symbols: test_main(int, char**) export DYLD_LIBRARY_PATH c++ -g -fPIC -shared -o "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/ libboost_test_exec_monitor.dylib" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/execution_monitor.o" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/test_tools.o" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/unit_test_parameters.o" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/unit_test_log.o" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/unit_test_monitor.o" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/unit_test_result.o" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/unit_test_suite.o" "libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/test_main.o" ...failed gcc-Link-action libs/test/build/bin/libboost_test_exec_monitor.dylib/gcc/debug/runtime- link-dynamic/shared-linkable-true/libboost_test_exec_monitor.dylib... gcc-Link-action libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/ libboost_unit_test_framework.dylib c++: unrecognized option `-shared' ld: can't locate file for: -lcrt0.o export DYLD_LIBRARY_PATH c++ -static -g -fPIC -shared -o "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/ libboost_unit_test_framework.dylib" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/execution_monitor.o" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/test_tools.o" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/unit_test_parameters.o" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/unit_test_log.o" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/unit_test_monitor.o" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/unit_test_result.o" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/unit_test_suite.o" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/unit_test_main.o" ...failed gcc-Link-action libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-static/shared-linkable-true/ libboost_unit_test_framework.dylib... gcc-Link-action libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/ libboost_unit_test_framework.dylib c++: unrecognized option `-shared' ld: Undefined symbols: init_unit_test_suite(int, char**) export DYLD_LIBRARY_PATH c++ -g -fPIC -shared -o "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/ libboost_unit_test_framework.dylib" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/execution_monitor.o" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/test_tools.o" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/unit_test_parameters.o" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/unit_test_log.o" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/unit_test_monitor.o" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/unit_test_result.o" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/unit_test_suite.o" "libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/unit_test_main.o" ...failed gcc-Link-action libs/test/build/bin/libboost_unit_test_framework.dylib/gcc/debug/ runtime-link-dynamic/shared-linkable-true/ libboost_unit_test_framework.dylib... gcc-Link-action libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_thread.dylib c++: unrecognized option `-shared' ld: Undefined symbols: _main export DYLD_LIBRARY_PATH c++ -g -fPIC -shared -o "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_thread.dylib" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/condition.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/mutex.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/recursive_mutex.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/thread.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/tss.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/xtime.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/once.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/exceptions.o" "libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/threadmon.o" ...failed gcc-Link-action libs/thread/build/bin/libboost_thread.dylib/gcc/debug/runtime-link- dynamic/shared-linkable-true/libboost_thread.dylib... ...failed updating 19 targets... ...skipped 6 targets... ...updated 113 targets... [aa:~/Library/Boost/boost-1.30.2] aelony%

2 1

Condition variable and const-correctness
by Weston Markham 21 Oct '03

21 Oct '03

It strikes me as odd that waiting on a condition variable is not const. It seems to me that, although one does expect the condition variable to change state, one is not actually requesting the change, but instead is merely detecting a change made by another thread. I can understand that, internally, the condition variable is probably keeping lists of waiting threads, which would need to be modified in order to satisfy the wait() call. From the point of view of the calling code, however, I think that this is irrelevant. Is there some other sense in which calling wait() can be considered to modify the condition variable? Weston Markham

3 2

filter iterator example fails concept checks
by Chris Saunders 21 Oct '03

21 Oct '03

I've tried to compile one of the examples from the filter_iterator documentation: main() { int numbers[] = { 0, -1, 4, -3, 5, 8, -2 }; const int N = sizeof(numbers)/sizeof(int); std::copy(boost::make_filter_iterator(numbers, numbers + N, std::bind2nd(std::greater<int>(), -2)), boost::make_filter_iterator(numbers + N, numbers + N, std::bind2nd(std::greater<int>(), -2)), std::ostream_iterator<int>(std::cout, " ")); std::cout << std::endl; } using a version of g++ 3.3.2 that has concept-checks enabled. In this case the compiler rejects both of the iterators returned by make_filter_iterator in the above code because they do not fulfill the InputIterator concept required by std::copy. This is because InputIterator requires the DefaultConstructable concept, and the predicate: std::bind2nd(std::greater<int>(),-2) , isn't default constructable. My question is this: is this type of iterator (non-default-constructable) safe to use in general even if it fails a conceptual requirement? Of course the above code runs as expected with a normal g++ build and I could always wrap the predicate in another object if I really wanted to use concept-checks... but I'm interested in whether the above code is considered normal and safe as it stands. Thanks for any insight. -Chris

2 1

RE: [Boost-users] Re: Linking STLPort 4.3 and Boost with VC7.0
by Ben Hutchings 21 Oct '03

21 Oct '03

David Abrahams <dave(a)boost-consulting.com> wrote: <snip> > > Thanks for the tips but how do i go about "..preprocessing > > your code and looking for suspicious #includes."? > > I never debugged the preprocess level before. > > Invoke your compiler with -E instead of -c (or /E instead of /c) and > look at the #include lines for the names of old-style headers. There are no #include directives in preprocessor output. There may be #line directives or similar lines stating filenames though.

1 0

First time using the boost libs and stuck horribly
by David Kowis 21 Oct '03

21 Oct '03

First of all, apologies if this information can be found somewhere else. I couldn't find it anywhere on the internet. Now to the real problem. I'm simply trying to utilize the boost libraries (filesystem in particular) in my program. I'm just trying to even run the example programs. I'm using Visual C++ 6.0 sp5. I figured out how to compile it by including the directory where boost is. So the example program compiles perfectly fine. Then the shit hits the fan, every reference to any boost object gets an unresolved external error. I have no clue why this is happening, and the most frustrating part is I cannot find information anywhere on the internet on how to make it work. I find lots of references telling me how great it is, but I cannot use it! Dave My compile output from visual c++ 6.0: -------------------------------------------------------------------------------- Compiling... path_test.cpp Linking... LINK : warning LNK4075: ignoring /INCREMENTAL due to /DEBUGTYPE specification path_test.obj : error LNK2001: unresolved external symbol "public: __thiscall boost::filesystem::path::path(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (??0path@filesystem@boost@@QAE@ABV?$basic_s tring@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z) path_test.obj : error LNK2001: unresolved external symbol "public: __thiscall boost::filesystem::path::path(char const *,enum boost::filesystem::path_format)" (??0path@filesystem@boost@@QAE@PBDW4path_format@12@@Z) path_test.obj : error LNK2001: unresolved external symbol "public: bool __thiscall boost::filesystem::path::is_complete(void)const " (?is_complete@path@filesystem@boost@@QBE_NXZ) path_test.obj : error LNK2001: unresolved external symbol "public: bool __thiscall boost::filesystem::path::has_branch_path(void)const " (?has_branch_path@path@filesystem@boost@@QBE_NXZ) path_test.obj : error LNK2001: unresolved external symbol "public: bool __thiscall boost::filesystem::path::has_relative_path(void)const " (?has_relative_path@path@filesystem@boost@@QBE_NXZ) path_test.obj : error LNK2001: unresolved external symbol "public: bool __thiscall boost::filesystem::path::has_root_directory(void)const " (?has_root_directory@path@filesystem@boost@@QBE_NXZ) path_test.obj : error LNK2001: unresolved external symbol "public: bool __thiscall boost::filesystem::path::has_root_name(void)const " (?has_root_name@path@filesystem@boost@@QBE_NXZ) path_test.obj : error LNK2001: unresolved external symbol "public: bool __thiscall boost::filesystem::path::has_root_path(void)const " (?has_root_path@path@filesystem@boost@@QBE_NXZ) path_test.obj : error LNK2001: unresolved external symbol "public: class boost::filesystem::path __thiscall boost::filesystem::path::root_path(void)const " (?root_path@path@filesystem@boost@@QBE?AV123@XZ) path_test.obj : error LNK2001: unresolved external symbol "public: class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __thiscall boost::filesystem::path::root_directory(void)const " (?root_directory@path@filesyst em@boost@@QBE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@XZ) path_test.obj : error LNK2001: unresolved external symbol "public: class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __thiscall boost::filesystem::path::root_name(void)const " (?root_name@path@filesystem@boost@@ QBE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@XZ) path_test.obj : error LNK2001: unresolved external symbol "public: class boost::filesystem::path __thiscall boost::filesystem::path::relative_path(void)const " (?relative_path@path@filesystem@boost@@QBE?AV123@XZ) path_test.obj : error LNK2001: unresolved external symbol "public: struct boost::iterator_adaptor<struct boost::filesystem::detail::path_itr_imp,struct boost::default_iterator_policies,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const *,struct std::bidirectional_iterato r_tag,int> __thiscall boost::filesystem::path::begin(void)const " (?begin@path@filesystem@boost@@QBE?AU?$iterator_adaptor@Upath_itr_imp@detail@filesystem@boost@@Udefault_iterator_policies@4@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@st d@@ABV67@PBV67@Ubidirectional_iterator_tag@7@H@3@XZ) path_test.obj : error LNK2001: unresolved external symbol "bool __cdecl boost::filesystem::boost_directory_name(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (?boost_directory_name@filesystem@boost @@YA_NABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z) path_test.obj : error LNK2001: unresolved external symbol "bool __cdecl boost::filesystem::boost_file_name(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (?boost_file_name@filesystem@boost@@YA_NABV? $basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z) path_test.obj : error LNK2001: unresolved external symbol "bool __cdecl boost::filesystem::posix_name(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (?posix_name@filesystem@boost@@YA_NABV?$basic_str ing@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z) path_test.obj : error LNK2001: unresolved external symbol "public: class boost::filesystem::path __thiscall boost::filesystem::path::branch_path(void)const " (?branch_path@path@filesystem@boost@@QBE?AV123@XZ) path_test.obj : error LNK2001: unresolved external symbol "public: class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __thiscall boost::filesystem::path::leaf(void)const " (?leaf@path@filesystem@boost@@QBE?AV?$ba sic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@XZ) path_test.obj : error LNK2001: unresolved external symbol "class boost::filesystem::path const & __cdecl boost::filesystem::check_posix_leaf(class boost::filesystem::path const &)" (?check_posix_leaf@filesystem@boost@@YAABVpath@12@ABV312@@Z) path_test.obj : error LNK2001: unresolved external symbol "bool __cdecl boost::filesystem::exists(class boost::filesystem::path const &)" (?exists@filesystem@boost@@YA_NABVpath@12@@Z) path_test.obj : error LNK2001: unresolved external symbol "public: __thiscall boost::filesystem::path::path(char const *)" (??0path@filesystem@boost@@QAE@PBD@Z) path_test.obj : error LNK2001: unresolved external symbol "public: class boost::filesystem::path & __thiscall boost::filesystem::path::operator/=(class boost::filesystem::path const &)" (??_0path@filesystem@boost@@QAEAAV012@ABV012@@Z) path_test.obj : error LNK2001: unresolved external symbol "public: void __thiscall boost::filesystem::detail::path_itr_imp::operator++(void)" (??Epath_itr_imp@detail@filesystem@boost@@QAEXXZ) path_test.obj : error LNK2001: unresolved external symbol "public: void __thiscall boost::filesystem::detail::path_itr_imp::operator--(void)" (??Fpath_itr_imp@detail@filesystem@boost@@QAEXXZ) Debug/path_test.exe : fatal error LNK1120: 24 unresolved externals Error executing link.exe. path_test.exe - 25 error(s), 1 warning(s) _ ._ _ , _ ._ (_ ' ( ` )_ .__) ( ( ( ) `) ) _) (__ (_ (_ . _) _) ,__) `~~`\ ' . /`~~` ,::: ; ; :::, ':::::::::::::::' _____________/_ __ \____________ David Kowis Computer Programmer ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

2 5

Numeric parsing of strings
by rlyon＠comgroup.net.au 21 Oct '03

21 Oct '03

Hi, Many applications are required to parse a string/file and extract numeric values. You can use sscanf or alternatively use regexp with numeric casting templates. I suprised that boost doesn't seem to contain conversion templates like: template < typename t_target > t_target decimal_cast( const std::string& arg ){ ... }; template < typename t_target > t_target octal_cast( const std::string& arg ){ ... }; template < typename t_target > t_target hex_cast( const std::string& arg ){ ... }; When you use these type of casts with regexp, you can construct simple robust parsers for reading numeric data from files, etc ..., in just a few lines of code. The lexical_cast and numeric_cast don't seem to cover these conversions. This is much better approach than using parsing framework like spirit/antlr. Shouldn't boost have this capability. Regards

1 0

Boost.threads: can't create static libraries under linux
by Brewer, Christopher 20 Oct '03

20 Oct '03

Hello, all- For some reason bjam doesn't build the 'boost.thread' static libraries for me (the shared libraries _do_ build properly, though). There are no errors, no warnings- they just don't get built. I'm working with boost-1.30.2 on Red Hat 9 using bjam 3.1.7 (the prebuilt binary from sourceforge). I've tried executing ./configure and swapping out 'user.hpp', but this has no effect. I'm mystified. Am I missing something obvious? Regards, Chris Brewer

2 1

[BUG]: Boost MP thread crasher: thread_cleanup key not being initialized
by Bobby Thomale 20 Oct '03

20 Oct '03

I believe I have found a crashing bug in the boost thread classes on MacOS X, in the MP threads implementation. I looked at the source and I think I have figured out what is wrong and how to fix it. The thread_cleanup function, which on the MP threads implementation is called each time a boost thread exits, assumes that the "cleanup key" has been initialized. If it hasn't been initialized (ie you aren't using any thread specific storage), it still calls MPGetTaskStorageValue with the uninitialized key index. Here are the first few lines of thread_cleanup: void thread_cleanup() { cleanup_handlers* handlers = reinterpret_cast<cleanup_handlers*>( MPGetTaskStorageValue(key)); if(handlers != NULL) { ... If you have not used any thread-specific storage, key is an uninitialized variable when this gets called. Not good. It looks like for the most part, rather than puking, MPGetTaskStorageValue is returning NULL when given an uninitialized key value, at least on 10.2.x. (I am doing some testing on the upcoming 10.3 release of MacOS X and noted that thread_cleanup crashes 100% of the time on this platform - I suspect MPGetTaskStorageValue is no longer returning NULL.) Since "key" is an uninitialized variable, I would think this would have unpredictable results and would crash occasionally even on 10.2.x, whenever "key" happened to start off as a value that was already in use maybe. It seems to me that we should simply make sure that the key is inited when calling thread_cleanup like so: boost::call_once(&init_cleanup_key, once); This makes sure that the key is inited, even if get_handlers is never called. (Adding that line of code to the beginning of thread_cleanup cleared up my crashing problems on 10.3 immediately.) Is that proper use of the call_once mechanism? Anyway, my first thought was to look at the implementations of threads on the other platforms, since they don't have this call_once call in their cleanup function before accessing the key either. It looks to me like, at least in the Windows code, the cleanup function is registered for the thread only during the get_handlers function, after the key is inited. If get_handlers is never called, the cleanup function never gets registered. In the Mac implementation, however, cleanup_thread is called directly by the thread proxy object at the end of thread execution, and it gets called even if get_handlers has never been called and the key has never been initialized. Here is a patch for my proposed fix. (I am sure there are other ways of fixing this too.) Comments, anyone? *** tss.orig.cpp Mon Oct 20 13:19:44 2003 --- tss.cpp Mon Oct 20 13:19:30 2003 *************** *** 126,131 **** --- 126,133 ---- void thread_cleanup() { + boost::call_once(&init_cleanup_key, once); + cleanup_handlers* handlers = reinterpret_cast<cleanup_handlers*>( MPGetTaskStorageValue(key)); if(handlers != NULL) -- Bobby --------------------------------------------------------------------- Bobby Thomale Senior Software Developer Inoveon Corporation http://www.inoveon.com/ ---------------------------------------------------------------------

1 0

[bgl] undirected_dfs to find cut-vertices
by Stephan Höfer 20 Oct '03

20 Oct '03

Hello, I build a visitor for an undirected graph which finds the cut-vertices of a given undireted graph or subgraph. I haven't found an implementation of the algorithm in the bgl. Maybe it would have been possible to use the predecessor_recorder for that. But then all the information which can be found directly while doing the df-search we have to find after having performed that search first. The interface of the undirected_dfs function doesn't take visitors via reference, so it wasn't possible to use that function. I had to call the detail::undir_dfv_impl function instead because that function takes a visitor reference and I had to recreate a function with the behaviour of the undirected_dfs. What reasons lead to the decision to disable passing a visitor by reference directly to undirected_dfs? What reasons lead to the decision to pass a const graph to a visitor function? Some useful things are disabled by that (but maybe also some bad things). Cheers, Stephan

2 1