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

Compiling Boost with PGI
by Ruediger Berlich 23 Apr '09

23 Apr '09

Hi there, I am trying to port my heavily Boost-based application to different compiler(-versions) . I was successful with Intel and various Linux-based gcc versions so far. Now I am trying my luck with the Portland group compiler in version 8. Corresponding compiler support seems to be available in Boost: ./tools/build/v2/tools/pgi.jam ./boost/config/compiler/pgi.hpp A "./configure --with-toolset=pgi" succeeds. The subsequent make, however, results in a plethora of error messages such as the following: gcc.compile.c++ bin.v2/libs/math/build/gcc/release/threading-multi/nextafter.o /bin/sh: line 1: -ftemplate-depth-128: command not found -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fP IC -DBOOST_ALL_NO_LIB=1 -DBOOST_MATH_TR1_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin. v2/libs/math/build/gcc/release/threading-multi/nextafter.o" "libs/math/build/../ src/tr1/nextafter.cpp" Looking into the pgi configuration files makes it appear as if the pgi support isn't finished yet. E.g. pgi.jam has a commented-out line # flags pgi.compile OPTIONS <threading>multi : -mt ; Indeed, pgCC does not accept this switch: $ pgCC -mt pgCC-Error-Unknown switch: -mt The above error message also makes it appear as if gcc options (e.g. "-Wall -pthread") are passed to pgCC. Can anyone comment on the status of PGI support by Boost ? The above happens on a system whose /etc/redhat-release states "Scientific Linux SL Release 4.0 (Beryllium)". The kernel is 2.6.9-42 . Scientific Linux is a Fedora-derivative, being used mostly in particle physics. Thanks and Best Regards, Ruediger

2 1

error while compiling application that uses a static lib that uses boost
by ChristinaDRS 23 Apr '09

23 Apr '09

Greetings all, I have a library called test which has a class that uses boost thread and mutex. here is how the includes in my .h file look: #include <boost/thread/mutex.hpp> #include <boost/thread.hpp> and here are the private vars: boost::mutex connectedPeersMutex_; boost::thread* listenThread_; in the .cpp file i have I use: #include <boost/bind.hpp> Now here is how I built my library with this Makefile: SRC = test1.cpp test2.cpp OBJ = $(SRC:.cpp=.o) OUT = libtest.a INCLUDES = -I. -I$$BOOST_ROOT CCFLAGS = -g CCC = g++ LDFLAGS = -g .SUFFIXES: .cpp default: $(OUT) .cpp.o: $(CCC) $(INCLUDES) $(CCFLAGS) -c $< -o $@ $(OUT): $(OBJ) ar rcs $(OUT) $(OBJ) clean: rm -f $(OBJ) $(OUT) Makefile.bak now I try to build a second application that simply uses the libtest.a like this: $ g++ -I ~/boost_1_38_0/ -I. main.cpp -omain -L/usr/local/lib/ -L. -ltest -lboost_thread-gcc41-mt-1_38 ./libtest.a(test1.o): In function `test1::StartServer(int, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, int)': /home/chris/test1.cpp:337: undefined reference to `boost::thread::thread(boost::function0<void, std::allocator<boost::function_base> > const&)' ./libtest.a(test1.o): In function `~ test1': /home/chris/test1.cpp:36: undefined reference to `boost::mutex::~mutex()' /home/chris/test1.cpp:36: undefined reference to `boost::mutex::~mutex()' /home/chris/test1.cpp:36: undefined reference to `boost::mutex::~mutex()' /home/chris/test1.cpp:36: undefined reference to `boost::mutex::~mutex()' /home/chris/test1.cpp:36: undefined reference to `boost::mutex::~mutex()' ./libtest.a(test1.o):/home/chris/test1.cpp:36: more undefined references to `boost::mutex::~mutex()' follow ./libtest.a(test1.o): In function `test1': /home/chris/test1.cpp:8: undefined reference to `boost::mutex::mutex()' /home/chris/test1.cpp:8: undefined reference to `boost::mutex::mutex()' ./libtest.a(test1.o): In function `boost::detail::thread::lock_ops<boost::mutex>::lock(boost::mutex&)': /usr/include/boost/thread/detail/lock.hpp:33: undefined reference to `boost::mutex::do_lock()' ./libtest.a(test1.o): In function `boost::detail::thread::lock_ops<boost::mutex>::unlock(boost::mutex&)': /usr/include/boost/thread/detail/lock.hpp:45: undefined reference to `boost::mutex::do_unlock()' collect2: ld returned 1 exit status Any idea why I am getting these undefined references? Thanks! Christina -- View this message in context: http://www.nabble.com/error-while-compiling-application-that-uses-a-static-… Sent from the Boost - Users mailing list archive at Nabble.com.

2 1

how to use boost.phoenix with std:for_each?
by Bruce Laing 23 Apr '09

23 Apr '09

Hi, I would like to do something like this: struct a_name { std::string name; }; a_name names[] = { std::string("one"), std::string("two") }; std::for_each( &names[0], &names[1], if_(1) [ std::cout << arg1.name ] ); but VC8 complains "error C2039: 'name' : is not a member of 'boost::phoenix::actor<Eval>'" Can anyone tell me what I'm doing wrong here? Thanks for your insights, - Bruce

2 1

Re: [Boost-users] [Statechart] Passing reference tocreate_processor()
by Andreas Huber 22 Apr '09

22 Apr '09

Hi Igor > I've got the same problem now. Is there > any solution or workaround so far? No, sorry. I haven't yet had sufficient time to find the root cause. I hope I'll get to it tomorrow. Regards, Andreas

1 0

[statechart] Question about do activities
by Bill Clark 22 Apr '09

22 Apr '09

In the boost::statechart documentation, on the UML mapping page, it says this about do activities: “A do activity can be simulated with a separate thread that is started in the entry action and cancelled (!) in the exit action of a particular state.” What's the significance of the exclamation point here? Is it suggesting that the thread should be killed rather than joined? I'm considering boost::statechart for a design where do activities will be a fundamental feature, so I'm wondering whether we might run into problems with this.

3 5

binding to new
by Noah Roberts 22 Apr '09

22 Apr '09

I have a factory that returns an instance of a concrete under an abstraction. It works by matching a "command" string to a command handler that is created and returned to the client. It's basically a stack of regex->creator pairs. The creator is a function that returns a pointer to the abstract type. I'd like to provide that function by binding to the new operator. Currently I have a static function in each concrete type that just calls new and I bind to it. I can't think of what syntax I would use to bind to new and am inclined to think it impossible, but I thought I'd ask.

2 1

Compiling exception/get_error_info.hpp in Visual Stuido UNICODE project
by Oleg V. Zhylin 22 Apr '09

22 Apr '09

Hi, I'm trying to compile my project in MS Visual Studio 2008 with UNICODE and _UNICODE symbols defined. This automatically makes std::string resolve to std::wstring. I'm having a problem compiling exception/get_error_info.hpp because of the following code struct strwrap { std::string str; char const * ptr; explicit strwrap( char const * s ): str(s), ptr(&str[0]) { } Error messages quite predictably say about type inconsistency, there's a copy of them below my signature. Is there a known way to tweak boost to build seamlessly with Visual Studio Unicode projects? WBR Oleg V. Zhylin ovz(a)yahoo.com g:\Program Files\boost\boost_1_38\boost\exception\get_error_info.hpp(30) : error C2664: 'std::basic_string<_Elem,_Traits,_Ax>::basic_string(const std::basic_string<_Elem,_Traits,_Ax>::_Alloc &)' : cannot convert parameter 1 from 'const char *' to 'const std::basic_string<_Elem,_Traits,_Ax>::_Alloc &' with [ _Elem=wchar_t, _Traits=std::char_traits<wchar_t>, _Ax=std::allocator<wchar_t> ] and [ _Elem=wchar_t, _Traits=std::char_traits<wchar_t>, _Ax=std::allocator<wchar_t> ] Reason: cannot convert from 'const char *' to 'const std::basic_string<_Elem,_Traits,_Ax>::_Alloc' with [ _Elem=wchar_t, _Traits=std::char_traits<wchar_t>, _Ax=std::allocator<wchar_t> ] No constructor could take the source type, or constructor overload resolution was ambiguous g:\Program Files\boost\boost_1_38\boost\exception\get_error_info.hpp(30) : error C2440: 'initializing' : cannot convert from 'std::allocator<_Ty>::value_type *' to 'const char *' with [ _Ty=wchar_t ] Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast g:\Program Files\boost\boost_1_38\boost\exception\get_error_info.hpp(30) : error C2439: 'boost::exception_detail::strwrap::ptr' : member could not be initialized g:\Program Files\boost\boost_1_38\boost\exception\get_error_info.hpp(24) : see declaration of 'boost::exception_detail::strwrap::ptr' g:\Program Files\boost\boost_1_38\boost\exception\diagnostic_information.hpp(60) : error C2664: 'std::basic_string<_Elem,_Traits,_Ax>::basic_string(const std::basic_string<_Elem,_Traits,_Ax>::_Myt &)' : cannot convert parameter 1 from 'std::basic_ostringstream<_Elem,_Traits,_Alloc>::_Mystr' to 'const std::basic_string<_Elem,_Traits,_Ax>::_Myt &' with [ _Elem=wchar_t, _Traits=std::char_traits<wchar_t>, _Ax=std::allocator<wchar_t> ] and [ _Elem=char, _Traits=std::char_traits<char>, _Alloc=std::allocator<char> ] and [ _Elem=wchar_t, _Traits=std::char_traits<wchar_t>, _Ax=std::allocator<wchar_t> ] Reason: cannot convert from 'std::basic_ostringstream<_Elem,_Traits,_Alloc>::_Mystr' to 'const std::basic_string<_Elem,_Traits,_Ax>::_Myt' with [ _Elem=char, _Traits=std::char_traits<char>, _Alloc=std::allocator<char> ] and [ _Elem=wchar_t, _Traits=std::char_traits<wchar_t>, _Ax=std::allocator<wchar_t> ] No constructor could take the source type, or constructor overload resolution was ambiguous

2 1

Re: [Boost-users] unwanted exported symbols in a DLL which statically links to Boost.Library
by John Dlugosz 22 Apr '09

22 Apr '09

> Date: Wed, 22 Apr 2009 15:22:31 +0200 > From: "Luca Cappa" <luca.cappa(a)sequoia.it> > Subject: [Boost-users] unwanted exported symbols in a DLL which > statically links to Boost.Library > To: boost-users(a)lists.boost.org > Message-ID: <op.ussh3tr5r4jy9l(a)vortex.homenet.telecomitalia.it> > Hello, > > I am creating a DLL using the VisualC++ 8sp1, which statically links to > Boost.Library, and also to another static library, which links to > Boost.Library statically too. > > In the export section of the built DLL I see, among the few public > functions which it should export, hundreds of exported functions like > the > ones below. I would really like to export the symbols the DLL defines > as > exported, and not anything else which is unexpectly exported, like the > ones shown below: > I'm not familiar with Boost's libs, but I am good with Windows, and DLL stuff in particular. So maybe I can offer some advice, which may be of help when combined with some information from others. I would agree that if the library containing those functions is static, it should not export anything. It's difficult to cause anything to be exported (nearly impossible for C++ decorated names, IME) other than by decorating the declaration of that function or variable, or the class containing it. On VC++, the decoration appears at the beginning and takes the form __declspec(dllexport) To unravel the macros and conditional compilation, pass one of the files through the preprocessor only. Do this in Visual Studio by opening the properties window for just the one CPP file (not the project itself). Under C/C++, Command Line, add the "/E" option, without the quotes, where you can type Additional Options. Then right-click on the filename in the solution explorer and choose to compile just that file. It won't actually compile, but it will produce another text file (I forget where it puts it). Change it back before Visual Studio gets confused. If "dllimport" is in that text somewhere, it is indeed doing that on purpose. TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

1 0

error while loading shared libraries
by ChristinaDRS 22 Apr '09

22 Apr '09

Greetings all, I first created a class for a library like this: library.h: class Library { public: Library() { }; ~Library() { }; void testLib(); }; library.cpp: #include "library.h" #include <boost/thread/mutex.hpp> #include <boost/thread.hpp> #include <iostream> using namespace std; void Library::testLib() { boost::thread* lt; boost::mutex mu; boost::mutex::scoped_lock lock(mu); cout << "test!" << endl; } I then created the static library like so: g++ -I ~/boost_1_38_0/ -c library.cpp ar rcs libtest.a library.o and then I created a main.cpp like so: #include "library.h" #include <iostream> using namespace std; int main() { Library l; l.testLib(); } now when I try to compile main.cpp like this: $ g++ -I ~/boost_1_38_0/ -I. main.cpp -o main -L/usr/local/lib/ -L. -ltest -lboost_thread-gcc41- now when I run main: $ ./main ./main: error while loading shared libraries: libboost_thread-gcc41-mt-1_38.so.1.38.0: cannot open shared object file: No such file or directory I get that error. Can anyone explain why? -- View this message in context: http://www.nabble.com/error-while-loading-shared-libraries-tp23175557p23175… Sent from the Boost - Users mailing list archive at Nabble.com.

2 1

unwanted exported symbols in a DLL which statically links to Boost.Library
by Luca Cappa 22 Apr '09

22 Apr '09

Hello, I am creating a DLL using the VisualC++ 8sp1, which statically links to Boost.Library, and also to another static library, which links to Boost.Library statically too. In the export section of the built DLL I see, among the few public functions which it should export, hundreds of exported functions like the ones below. I would really like to export the symbols the DLL defines as exported, and not anything else which is unexpectly exported, like the ones shown below: boost::archive::detail::oserializer<class boost::archive::xml_oarchive,struct sqy::Vector2<float> >::oserializer<class boost::archive::xml_oarchive,struct sqy::Vector2<float> >(void) boost::archive::detail::oserializer<class boost::archive::xml_oarchive,struct sqy::Vector2<float> >::oserializer<class boost::archive::xml_oarchive,struct sqy::Vector2<float> >(void) boost::archive::detail::oserializer<class boost::archive::xml_oarchive,struct sqy::Vector2<double> >::oserializer<class boost::archive::xml_oarchive,struct sqy::Vector2<double> >(void) In my static library, which statically link to the Boost.Serialization library, I have the following code which explicitly instantiate some template type on a set of a priori known datatypes: template MYLIB_API struct sqy::Vector2<int>; template MYLIB_API struct sqy::Vector2<float>; template MYLIB_API struct sqy::Vector2<double>; template MYLIB_API struct sqy::Vector2<size_t>; #define INSTANTIATE_VECTOR2_SERIALIZATION(x)\ template void MYLIB_API Vector2<x>::serialize<boost::archive::xml_oarchive> (\ boost::archive::xml_oarchive&, const unsigned int);\ template void MYLIB_API Vector2<x>::serialize<boost::archive::xml_iarchive> (\ boost::archive::xml_iarchive&, const unsigned int); INSTANTIATE_VECTOR2_SERIALIZATION(int); INSTANTIATE_VECTOR2_SERIALIZATION(float); INSTANTIATE_VECTOR2_SERIALIZATION(double); INSTANTIATE_VECTOR2_SERIALIZATION(size_t); Notice that, when the DLL is created, MYLIB_API is defined like # define MYLIB_API so i wonder where those symbols above comes from? Anyone could help me to remove from the DLL exporting section those unwanted symbols? Many thanks in advance, Luca

2 1