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
reference to 'shared_ptr' is ambiguous #8
Comments
Why on earth does your compiler do this, despite the boost type being explicitly pulled in by the "using" directive? Maybe explicitly telling the compiler to not use C++11 might help. |
This is specifically happening using clang's libc++ standard library, which is the default under OS X 10.9. Not sure it can be made to not use C++11. |
It might be worth trying boost::tr1 for the smart pointers; according to the docs it should simply pull in std::tr1 if available, but boost's implementation otherwise. |
…tion otherwise; we're using <boost/tr1/memory.hpp> to pull in either. Should fix GitHub issue #8. corresponds to Perforce change 6132.
should be fixed in master now. |
Upstream has fix for {boost,std::tr1}::shared_ptr ambiguity, but now there's {std::tr1,std}::shared_ptr ambiguity. See: POV-Ray/povray#8 POV-Ray/povray#31
…tion otherwise; we're using <boost/tr1/memory.hpp> to pull in either. Should fix GitHub issue #8. corresponds to Perforce change 6132.
Building povray 3.7.0.0 on OS X 10.9 has the following trouble:
In MacPorts we are replacing all occurrences of
shared_ptr
withboost::shared_ptr
to work around this.The text was updated successfully, but these errors were encountered: