Open GoogleCodeExporter opened 9 years ago
Please post the entire error message.
Original comment by jbe...@gmail.com
on 9 Jan 2015 at 1:43
In file included from D:\Projects\MyProject\deps\yaml-cpp\src\convert.cpp:3:
In file included from
D:/Projects/MyProject/deps/yaml-cpp/include\yaml-cpp/node/convert.h:17:
In file included from
D:/Projects/MyProject/deps/yaml-cpp/include\yaml-cpp/node/impl.h:13:
In file included from
D:/Projects/MyProject/deps/yaml-cpp/include\yaml-cpp/node/detail/node.h:13:
In file included from
D:/Projects/MyProject/deps/yaml-cpp/include\yaml-cpp/node/detail/node_ref.h:13:
D:/Projects/MyProject/deps/yaml-cpp/include\yaml-cpp/node/detail/node_data.h:32:
20: error: base class 'boost::noncopyable' (aka
'boost::noncopyable_::noncopyable') has private copy constructor
class YAML_CPP_API node_data : private boost::noncopyable {
^
D:/msys2/mingw64/include\boost/core/noncopyable.hpp:38:7: note: declared
private here
noncopyable( const noncopyable& );
^
D:/Projects/MyProject/deps/yaml-cpp/include\yaml-cpp/node/detail/node_data.h:32:
20: note: implicit copy constructor for 'YAML::detail::node_data' first
required here
class YAML_CPP_API node_data : private boost::noncopyable {
^
D:/Projects/MyProject/deps/yaml-cpp/include\yaml-cpp/node/detail/node_data.h:32:
20: error: 'operator=' is a private member of 'boost::noncopyable_::noncopyable'
class YAML_CPP_API node_data : private boost::noncopyable {
^
D:/msys2/mingw64/include\boost/core/noncopyable.hpp:39:20: note: declared
private here
noncopyable& operator=( const noncopyable& );
^
D:/Projects/MyProject/deps/yaml-cpp/include\yaml-cpp/node/detail/node_data.h:32:
20: note: implicit copy assignment operator for 'YAML::detail::node_data' first
required here
class YAML_CPP_API node_data : private boost::noncopyable {
^
2 errors generated.
Original comment by morfi...@gmail.com
on 9 Jan 2015 at 1:50
I don't understand where the implicit copy constructor for node_data is
actually requested. This is the whole error message?
Original comment by jbe...@gmail.com
on 9 Jan 2015 at 2:10
Yes that's whole message: i don't understand as well. Those could be just a bug
of clang on Windows
Original comment by morfi...@gmail.com
on 10 Jan 2015 at 11:11
Original issue reported on code.google.com by
morfi...@gmail.com
on 9 Jan 2015 at 10:28