IMHO it's not requirement to use -pthread on linux - especially when it's
not documented. I think usage of -D_REENTRANT for compiling and -lpthread
for linking should be enough.
Maybe - I don't have a linux box to check on right now - doing a:
g++ -dumpspecs | grep thread
will tell you
On Saturday 23 August 2003 07:18 am, John Maddock wrote:
One more thing: what exactly can go wrong with 1.30.0 if
-pthread isn't used? Is it boost specific or a general thing
(e.g. issues w/ respect to libstdc++)?
A general thing - without this then:
Your std lib is not thread safe.
On Sat, 23 Aug 2003, John Maddock wrote:
One more thing: what exactly can go wrong with 1.30.0 if
-pthread isn't used? Is it boost specific or a general thing
(e.g. issues w/ respect to libstdc++)?
A general thing - without this then:
Your std lib is not thread safe.
Your C lib is
One more thing: what exactly can go wrong with 1.30.0 if
-pthread isn't used? Is it boost specific or a general thing
(e.g. issues w/ respect to libstdc++)?
A general thing - without this then:
Your std lib is not thread safe.
Your C lib is not thread safe.
g++ will not emit thread safe
Geurt Vos wrote:
I mean, is boost bjammed correctly for thread
support? The thing is that the following code
segfaults on '-pthread'
#include boost/filesystem/operations.hpp
int main()
{
*boost::filesystem::directory_iterator(/);
}
# g++ -o test test.cpp -lboost_filesystem
#
