Closed
Bug 862759
Opened 11 years ago
Closed 11 years ago
js/src fails to build with -std=c++11
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 877937
People
(Reporter: jbeich, Unassigned)
References
Details
I'm using clang32/libc++ and it seems to be stricter than g++48/libstdc++. js/src/frontend/ParseMaps.cpp:137:16: error: explicit instantiation of 'js::frontend::AtomDecls' must occur in namespace 'frontend' template class AtomDecls<FullParseHandler>; ^ ../../../js/src/frontend/ParseMaps.h:386:7: note: explicit instantiation refers here class AtomDecls ^ js/src/frontend/ParseMaps.cpp:138:16: error: explicit instantiation of 'js::frontend::AtomDecls' must occur in namespace 'frontend' template class AtomDecls<SyntaxParseHandler>; ^ ../../../js/src/frontend/ParseMaps.h:386:7: note: explicit instantiation refers here class AtomDecls ^ 2 errors generated.
Comment 1•11 years ago
|
||
Are you adding -std=c++11 to CXXFLAGS or something? I imagine this sort of addition to CXXFLAGS or to CXX is somewhat low on the things-to-support totem. :-) It's a pretty fundamental addition -- I doubt we want this configurable. That said. If we care, the spot-fix is easy enough, and probably desirable regardless of -std=... supportedness or not. I imagine these things will keep occasionally breaking from unwitting changes, unless SpiderMonkey converts to -std=gnu++0x. We eschewed that for a long time in the interests of C compatibility (C++11's standard headers don't always play well with C's standard headers). But C compatibility is no longer an issue, so we might be able to follow up on this now. Any chance you might be able to do that?
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•