https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105710
--- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Eric Gallager from comment #7) > > (as I have said several times, the idea of configure is to choose the > > correct settings for the target _automatically_ - extra config options > > should only be added if there is a very good reason and you know exactly > > what they do). > > Well we could at least make the error happen earlier rather than letting it > turn into an ICE. I think making the configure script smarter about whether > TLS works or not could be worthwhile; see bug 53504 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 :)
