X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=sf59MuRabAyKvT7K xm4XzfMmf+O2GWinFm8YTkAwDsU4xAmqdNqzXjIDVDzSE0Ba6/1CQcQZNTBhiKts Us4IEOkUnCYcI4sfjMW4D+R7phsoDK9z13kNh3vZo+8VP0fTcNhUUILFtBcrTqnG hPbms8GV0FdUavJcMHLM5SwdvIA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=8VMyFrfId58LXP4h1BxsEu k4vsI=; b=sAB90JpERNnjroktLTlXvhlXn+fFvFcdf2KDzFjipy8l36e9uiMS8x N8yqZzpGYIsfeuDCSe7SWOeSFmsWG1CPktS/LjZIt6awU2UMIfbMU3DzQ1VDjuZd 8vezd44MuC2gWvKnoqnmNvA2XfrWldg9nDrZBIHVQovJEfoClkDoE= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-7.6 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=i686x86_64, i686,x86_64, H*M:1680 X-HELO: smtp-out-so.shaw.ca X-Authority-Analysis: v=2.2 cv=B4DJ6KlM c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=N659UExz7-8A:10 a=x7bEGLp0ZPQA:10 a=mDV3o1hIAAAA:8 a=93WjmWnU5ZTotJh4qGUA:9 a=pILNOxqGKmIA:10 a=_FVE-zBwftR9WsbkzFJk:22 Reply-To: Brian DOT Inglis AT Shaw DOT ca Subject: Re: Which is it -pc- or -unknown- To: cygwin AT cygwin DOT com References: <29b66287-6bd7-4e82-b35d-12a735c2070b AT gmail DOT com> From: Brian Inglis Message-ID: <3415f3b3-1680-9837-3f35-e011cf0a5aa9@Shaw.ca> Date: Tue, 17 Oct 2017 23:26:08 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfAkxjmsCm5m6cDjReQA7kKvnsF4NOjxvV65OqtquG6W9VOSI7r7J6fjFCYOwv/SkrpgDl/5kI02OLRwn4eryeWYBinbF9dnR2aLlQHO99I7nk3xpljA/ Pw/08ReeCaf7Vz3LBscGc/KyZ7tG0pgLJ6id07oGRYSoVeYTGLSC5Rm0 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