https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105710
--- Comment #9 from Sergey Fedorov <vital.had at gmail dot com> --- (In reply to Iain Sandoe from comment #8) > If we try to do this for every irrelevant configure option, that's going to > be quite a lot of work. > > Really [IMO, at least], configure options are not intended for end-users > - the goal for end users is that: > > configure --prefix=xxxxxx && make && install > > should 'just work' (OK, we don't quite achieve that, but actually we're > quite close) > > adding out-of-band configure options is for distributions and expert use > (we assume distributions are expert in the options they need to apply to > customise the install). > > However, of course, if you want to write patches to respond to all the > options > that Darwin does not need, I'm happy to review :) I agree with Iain here, in fact it is a problem with Macports, since it’s `--disable-tls` option lists a reason totally unrelated to PPC or Darwin version: ># see https://lists.macports.org/pipermail/macports-dev/2017-August/036209.html ># --disable-tls does not limit functionality ># it only determines how std::call_once works >configure.args-append \ > --disable-tls Then it was me who misunderstood Iain’s reply in my PR to Ruby. I thought that Macports disables TLS for no clear reason, while Ruby wants it provided by the compiler, and tried to build it with `--enable-tls`. Sorry for a confusion. I just had an impression that all ICEs have to be reported.
