Re: a plea to change the default std lib clang adds if none is specified on the build line

On 2018-03-11, at 8:07 PM, Kenneth F. Cunningham wrote: > > > This is committed to trunk. I'm not sure if this made it into clang-6.0 or > not, but there was a lot of talk about making sure it did. > Must be. That commit was r320250 and the current clang-6

Re: a plea to change the default std lib clang adds if none is specified on the build line

On 2018-03-11, at 5:39 PM, Mojca Miklavec wrote: > > This is pretty similar to https://trac.macports.org/ticket/53634 > except that I don't have a patch for that. > > Mojca I think the clang'ers have taken care of that for you. They skipped making the default c++11 and jumped to c++14, though

Re: a plea to change the default std lib clang adds if none is specified on the build line

On 12 March 2018 at 00:08, Kenneth F. Cunningham wrote: > 1 minute summary, no gobbledygook: > > When clang sees a build line, if there is no -stdlib=Something specified, it > adds -stdlib=libstdc++ on systems up to 10.8, and -stdlib=libc++ on 10.9 and > above. > > If the older OS is set up to us

a plea to change the default std lib clang adds if none is specified on the build line

1 minute summary, no gobbledygook: When clang sees a build line, if there is no -stdlib=Something specified, it adds -stdlib=libstdc++ on systems up to 10.8, and -stdlib=libc++ on 10.9 and above. If the older OS is set up to use -stdlib=libc++, then all these ports break, and need painful man