https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80781
--- Comment #9 from René J.V. Bertin <rjvbertin at gmail dot com> --- redi at gcc dot gnu.org wrote on 20170517::08:56:33 re: "[Bug target/80781] Feature request: build option to use libc++ instead of libstdc++ for increased usability on Mac" >https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80781 >> Meaning "that G++ will one day have this kind of support for libc++"? Is >> there a timeline or something? > >No. Somebody has to do the work. It will get into GCC if somebody does the >work, but not before then. What's the most efficient way (recipe) to end up with a build dir in which one can do incremental builds (= regular development)? The build script I've been using until now doesn't allow this reliably, forcing me to go through the whole 3-pass build each time. With efficient I here mean both in time and in terms of disk footprint. I'd expect that one ought to be able to rebuild GCC x.y.z from its own sources in a single pass because it's already proven to be able to do that, so is it possible to create a clean 1-pass build directory, configure and build it to develop smallish modifications to the driver like we're discussing here?
