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? Don't give me the historical reasons idea. Scenario: I know nothing of your *chosen* x86_64-pc-cygwin. I have found a new compiler toolchain I want to build from source. I use the defaults for the configure script. I end up with host tools of x86_64-unknown-cygwin. This now doesn't match your *chosen* x86_64-pc-cygwin. Scenario: I know nothing of your *chosen* x86_64-pc-cygwin. I download the latest version of binutils I use the defaults for the configure script. I end up with host tools of x86_64-unknown-cygwin. This now doesn't match your *chosen* x86-64-pc-cygwin. What is your angst toward changing the *default* to match the *chosen*? -- 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
