On 10/20/2017 2:44 PM, Brian Inglis wrote: > On 2017-10-20 11:41, Marco Atzeri wrote: >> On 20/10/2017 17:44, cyg Simple wrote: >>> On 10/20/2017 11:24 AM, >>> Why is it different? Give a reason not just some lame excuse. >> This is extremely rude, in my opinion. > > He's not asking the question he needs answered and is getting exasperated. >
I asked the question I wanted to ask, it was answered. >> You don't tell the brewer how to make the beer. > > I think the home brewer wants to make the standard brew, but no one is > explaining how to get "./configure && make" to produce the *PC* product, > instead > of some /unknown/ swill. ;^> > This isn't the question that needed answered. Sorry but I'm only talking about the default vendor from config.guess versus the chosen vendor and don't need help with ./configure && make. Erik Blake finally supplied a modicum of a reason why -unknown- is used but wasn't insistent that it needed to stay -unknown-. Feel free to tell me why you think config.guess should supply a default vendor of -unknown- for Cygwin even when config.sub doesn't? The purpose of config.guess is to supply configure the default build environment. If the host isn't supplied to configure then it defaults to match the build string. Since the build environment for Cygwin is x86_64-pc-cygwin then config.guess should default to that. This isn't a problem with most packages because they don't provide tools based on the host triplet. However, there are packages that do use the host triplet to provide a hosted set of tools. -- 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
