On 10/20/2017 11:24 AM, Yaakov Selkowitz wrote: > On 2017-10-20 08:28, cyg Simple wrote: >> On 10/19/2017 4:33 PM, Yaakov Selkowitz wrote: >>> 2) the output of config.guess is a default and does NOT reflect, or need >>> to match, our chosen triplet. There is nothing to fix in config.guess. >> >> Fine, it doesn't have to match, why don't you want it to? > > Because there is no correlation, is completely normal, and therefore no > need to special case Cygwin. >
What is *normal* about it? Just because other's do it? I gave scenarios in the mail which you elided from your response which give credence to a reason to change it. There is nothing that is *normal* in any scenario of config.guess. It is what the maintainers decide. You've not given a reason for the decision to make the *default* not match the *chosen* vendor. You just stand on the podium of unreason to state something as normal that has no merit in being normal. Doing so doesn't make Cygwin a special case. Yes, I can override the default, but I shouldn't have to is my reasoning of normal. In my sense of reasoning the normal should be the *default* matching the *chosen*. Why is it different? Give a reason not just some lame excuse. -- cyg Simple -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
