Boost C++ Libraries: Ticket #6124: Problem with copy_file in 1.47

morandidodo@… — Thu, 17 Nov 2011 08:17:05 GMT

I found a possible cause. Take this piece of code as test:

#include <boost/filesystem.hpp>
using namespace boost::filesystem;
int main()
{
   copy_file("a", "b");
   return 0;
}

I'm using g++ 4.5.2, and I noticed the problem occurs only when I compile the code with -std=c++0x. What I don't know is if the problem is related to the boost library or the compiler. However if I use boost 1.42 (the library provided from my Linux distribution) everything goes well.

Any suggestion? -- dodomorandi

anonymous — Mon, 21 Nov 2011 01:07:50 GMT

I'm experiencing the same problem with g++ 4.6.1 with -std=c++0x.

anonymous — Mon, 28 Nov 2011 17:34:37 GMT

Just another information, maybe it could be useful: I just installed the new Linux Mint 12. The problem is reproducible with default packages. Boost is 1.46.1, g++ 4.6.1.

status, component changed; resolution set

morandidodo@… — Tue, 29 Nov 2011 18:35:20 GMT

status new → closed
resolution → fixed
component filesystem → Building Boost

Got the problem - finally! It's necessary to build the Boost library using the "-std=c++0x" flag, like this: ./b2 cxxflags="-std=c++0x"

I think it's quite important to check before the compilation (using autoconf scripts, cmake scripts and so on) if the compiled libraries can be linked with the "c++0x" flag.

However, anyone knows if there's a reason to compile the Boost without c++0x? It could be possible to compile programs using the C++03 standard? If it's completely retro-compatible maybe it could be useful to enable the c++0x flag by default, isn't it?

-- dodomorandi

Beman Dawes — Fri, 24 Oct 2014 16:01:18 GMT

#6124, #6779, and #10038 are all the same problem. The private library interface has been changed to use a plain-old C++03 enum. This is the fix suggested by Andy in 6779.

The fix was too late for 1.57 beta 1, but should be in the final 1.57 release.

Thanks for your patience,

--Beman