This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Which is it -pc- or -unknown-
On 10/17/2017 7:39 PM, Brian Inglis wrote:
> On 2017-10-17 15:31, cyg Simple wrote:
>> On 10/17/2017 3:45 PM, Brian Inglis wrote:
>>> On 2017-10-17 13:16, cyg Simple wrote:
>>>> The config.guess file[1] is confused.
>>>> 840 i*:CYGWIN*:*)
>>>> 841 echo ${UNAME_MACHINE}-pc-cygwin
>>>> 842 exit ;;
>>>> -----
>>>> 870 amd64:CYGWIN*:*:* | x86_64:CYGWIN*:*:*)
>>>> 871 echo x86_64-unknown-cygwin
>>>> 872 exit ;;
>>>> The GCC executable is x86_64-pc-cygwin-gcc.exe but config.guess on my
>>>> system gives x86_64-unknown-cygwin so specifying a fully qualified host
>>>> doesn't find the executable file. So which should it be?
>>>> [1]http://git.savannah.gnu.org/cgit/config.git/tree/config.guess?id=c003e5cb947924ca5edd25c3b840aaa373c66b28
>>> That part of the triplet is defined as vendor, so it was probably initially
>>> Intel, then compatibles came out and that was genericized to PC, then someone
>>> objected and discussed and came up with Unknown, rather than say Any or None.
>>> It may reflect development ages of projects, autotools, defaults on projects, or
>>> project politics.
>>> Some projects still use PC, which may be a project override, others use Unknown,
>>> which should be the default in current releases of autotools.
>> So config.guess needs to change, correct? I thought the I had
>> remembered the discussion that it should be -unknown- for Cygwin. But
>> the GCC distribution is giving us -pc- instead which means the
>> maintainer specified the target as such. That needs to change as well.
>> I'm on x86_64 I bet x86 will be -pc- from config.guess just by the way
>> it's coded. Confusing!
>
> You might want to diff the upstream config.{guess,sub} with those from
> /usr/share/automake1.{14,15}/ as those are the latest, and earlier releases to
> see if they are just old, in case there are project customizations.
> You can then decide whether you want to look further at how much of the project
> automake infrastructure you want to upgrade, or check if the project has looked
> at, or is working on, doing that.
> If you do so, you could look at offering that back upstream.
>
Brian, I quoted the git master of config.guess in my original mail.
My concern is that on my 64bit Cygwin version config.guess guesses the
build as x86_64-unknown-cygwin but x86_64-pc-cygwin-gcc.exe is
distributed. Therefore there is a mismatch between what the maintainer
gives us from the GCC distribution and what the upstream config.guess
gives us. This leads to not being able to find
x86_64-unknown-cygwin-gcc.exe.
--
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