http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46333
--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2010-11-06 17:24:11 UTC --- On Sat, 6 Nov 2010, jay.krell at cornell dot edu wrote: > One person's machine has g++ 3.3. In the discussions of what the requirements would be for building with C++, I think it was generally accepted that the answer would be the intersection of C++98 with what is supported by some baseline GCC version - and that at least 3.4, maybe 4.0 or 4.1, would be OK to take as that baseline. (PPL is a C++ library that won't build with versions older than 4.0, so anyone building a Graphite-enabled compiler is using a C++ compiler more recent than 3.4 already.) Yes, we should have a configure test that rules out known-too-old compilers. > Another's g++ produces executables that don't run, can't find libstdc++. For build = host, a configure test for that may be useful as well. > On that machine, I'm instead trying /usr/bin/CC which is SunStudio 12. If that supports C++98 at least as well as GCC 3.4 does, then it ought to work - and having people testing such things will be very useful for verifying that we aren't introducing accidental G++ dependencies when making C++ builds a requirement. You may be the first person testing non-G++ C++ builds.
