Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenVRML 0.18.9 does not compile with Boost 1.65.1 #3

Open
raphael-st opened this issue Nov 13, 2017 · 3 comments
Open

OpenVRML 0.18.9 does not compile with Boost 1.65.1 #3

raphael-st opened this issue Nov 13, 2017 · 3 comments

Comments

@raphael-st
Copy link

This patch solves some of the problems, but now I get

In file included from libopenvrml/openvrml/local/uri.cpp:21:
In file included from libopenvrml/openvrml/local/uri.h:26:
In file included from /opt/local/include/boost/spirit/include/phoenix1.hpp:11:
In file included from /opt/local/include/boost/spirit/home/classic/phoenix.hpp:18:
/opt/local/include/boost/spirit/home/classic/phoenix/special_ops.hpp:62:48: error: no member named 'complex' in namespace 'std'
template <typename T> struct rank<PHOENIX_STD::complex<T> >
                                  ~~~~~~~~~~~~~^
/opt/local/include/boost/spirit/home/classic/phoenix/special_ops.hpp:62:56: error: 'T' does not refer to a value
template <typename T> struct rank<PHOENIX_STD::complex<T> >
                                                       ^
/opt/local/include/boost/spirit/home/classic/phoenix/special_ops.hpp:62:20: note: declared here
template <typename T> struct rank<PHOENIX_STD::complex<T> >
                   ^

See the corresponding MacPorts ticket.

@cooljeanius
Copy link

Is this project still even alive? The most recent commit is from almost 5 years ago now...

@bradenmcd
Copy link
Owner

Is this project still even alive? The most recent commit is from almost 5 years ago now...

Not really. Anyone interested in carrying it forward should fork it.

@cooljeanius
Copy link

Is this project still even alive? The most recent commit is from almost 5 years ago now...

Not really. Anyone interested in carrying it forward should fork it.

...so maybe mark the repo as "archived" then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants