On 2017-10-17 21:29, cyg Simple wrote:
> On 10/17/2017 7:49 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
>>
>> There are also similar confusions and differences between projects and
>> distros
>> about use of x86_64 (or x86-64) and amd64. You may have come across others.
>>
>
> I'm only concerned with Cygwin at the moment. As I understand it the we
> should distribute x86[_64]-unknown-cygwin-*.exe and not as
> x86[_64]-pc-cygwin-*.exe We also need to correct config.guess for the
> i*:CYGWIN*:* match.
It seems that i686-pc-... on lines 840... is common, probably for historical
reasons, and that may be okay for 32 bit builds but I don't know the Cygwin
history here, and x86_64-unknown-... should be selected for 64 bit builds in
lines 870...
Packages for current 32 and 64 bit binutils, cygwin32-..., and gcc... are
prefixed with or found under {i686,x86_64}-pc-cygwin, so you might have to
change the vendor field in config.guess, if you want to stay consistent.
Packages emacs, octave, and pkg-config are the only ones I can find using
x86_64-unknown-cygwin prefix on 64 bit, none with i686-unknown-cygwin on 32 bit.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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
