Re: [Boost-bugs] [Boost C++ Libraries] #6124: Problem with copy_file in 1.47

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #6124: Problem with copy_file in 1.47
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2011-11-29 18:35:21

#6124: Problem with copy_file in 1.47
------------------------------------+---------------------------------------
  Reporter:  morandidodo@…          |       Owner:  bemandawes                 
      Type:  Bugs                   |      Status:  closed                     
 Milestone:  To Be Determined       |   Component:  Building Boost             
   Version:  Boost 1.47.0           |    Severity:  Problem                    
Resolution:  fixed                  |    Keywords:  filesystem copy_file linker
------------------------------------+---------------------------------------
Changes (by morandidodo@…):

  * status:  new => closed
  * resolution:  => fixed
  * component:  filesystem => Building Boost

Comment:

 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

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/6124#comment:4>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.