Summary: | cc1plus: error: unrecognized command line option "-std=c++11" | ||
---|---|---|---|
Product: | Mesa | Reporter: | Vinson Lee <vlee> |
Component: | Mesa core | Assignee: | mesa-dev |
Status: | RESOLVED INVALID | QA Contact: | mesa-dev |
Severity: | normal | ||
Priority: | medium | CC: | baker.dylan.c, emil.l.velikov |
Version: | git | Keywords: | bisected, regression |
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Vinson Lee
2018-12-22 07:12:23 UTC
what compiler and what version? It wouldn't surprise me if old versions of gcc (Say 4.2) doesn't actually support C++11. Actually, it looks like std=c++11 was added in GCC 4.7, and before that you had to use std=c++0x. Clang added support for std=c++11 it looks like. https://gcc.gnu.org/projects/cxx-status.html#cxx11 https://clang.llvm.org/cxx_status.html Given the patch in question explicitly adds CXX11_CXXFLAGS in a section that is only taken into account when llvm is enabled the llvm version would also be relevant. AFAIR the last version before llvm-7 that didn't advertise -std=c++11 was something like llvm-3.9, and there was a patch proposed by Emil that would bump the minimum required version to 5.0 (it didn't land yet, I guess because there was some andorid WIP patch in the series). With that support for -std=c++11 would become a requirement for builds that enable llvm. AFAICT we probe if the compiler supports -std... before using it. If somehow that's not the case we ought to fix that, or fallback to one that owrks. Patches welcome :-) I haven't seen any other reports of this, so I'm going to remove it rom the 19.0 blocker. I don't think it's worth it to block the release. autotools builds have been removed from Mesa. Closing. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.