> Joe Buck <[EMAIL PROTECTED]> writes: > >>I think that the decision should be made at configure time, by checking > >>the #include headers to see if they are C++-ready. Look for the string > >>"__cplusplus" in some set of standard headers, if it is not found, > >>assume that we'll need implicit extern C. For cross-builds, we still > >>have a path to the headers to be checked.
Ian Lance Taylor wrote: > >It would be hard to make that completely reliable for embedded systems > >development, where the header files may or not be available in any > >standard place at the time that gcc is configured. On Tue, May 10, 2005 at 04:30:43PM -0600, E. Weddington wrote: > E.g. the AVR target, which normally uses avr-libc: > <http://savannah.nongnu.org/projects/avr-libc/> > but only builds avr-libc after gcc is built. Right, but you don't need the answer to the question until it's time to build libstdc++, and you can't build libstdc++ without a C library. So can't the test be deferred until that point?
