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=WBMCF1fF5PsKwbFU
	rJkM4A9nXQAYF8Wy9DdUKsolSPRqTbskZ02RQAqB7RLPBBSOvKt7x3G0VA7uDV8/
	Hi0Old3mbXxh0HOLD1PZzRjjEO8v2nCcVrjhLmGXpkGKTEu87yAr1Y0+wbSo5dyo
	Aef5LRkRTZM3JeMjHhMQ5gTTMWs=
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=W1VEe88h+VkYZrgkqyanBX
	cFIXk=; b=LAgc41OZJUz18/CGZ1pH1d7z5A1qc65kfAE8oYof6uC6xXWuF5DyxJ
	1z23U1SxFlMkZ4vIZJZ4QnmmnnpRjZ911nFBE32M6rWnLt8kXJRm5bRM8NHkDLma
	p1HDuA0ZSj2U+bj2GB5mNy9+z2I1WX//M/k6ai1Ee2q7r3vnxO6S4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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=-1.9 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=OPs, op's, OP's, phpsrc
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=NEAV23lmAAAA:8 a=QGXrikmFOznZpgfYES8A:9 a=pILNOxqGKmIA:10
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: Which is it -pc- or -unknown-
To: cygwin AT cygwin DOT com
References: <a9cce58b-13c4-510e-e93a-188ac407d95c AT gmail DOT com> <59e939fc DOT 21539d0a DOT 6c79e DOT 530e AT mx DOT google DOT com> <54f3b5d4-bc4d-f03e-5c7b-0f983f0783e8 AT cygwin DOT com>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID: <b550b872-0626-016e-ad5f-97b3a94def2d@SystematicSw.ab.ca>
Date: Thu, 19 Oct 2017 21:19:34 -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: <54f3b5d4-bc4d-f03e-5c7b-0f983f0783e8@cygwin.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfLn0QIl/uNW0Htn/9N77Hz8Q3sz8CZvs/f6ws7dQWaEh1o2P9kWnEFCMkDZqz79NEct7PczI8J16/yR4XdwD9uT2lQJyfVjKauU7W1lJFo/kQLwuOQ0b Mh/OQRH9VJf4iC1G/33wlZhhqxK/u5291d1nnwCRm4b1BDw5zpQDtEQ9ZNQ5WZQ5NLksDSI9NwITLA==
X-IsSubscribed: yes

On 2017-10-19 19:11, Yaakov Selkowitz wrote:
> On 2017-10-19 18:49, Steven Penny wrote:
>> On Thu, 19 Oct 2017 17:00:12, cyg Simple wrote:
>>> So says you!  The vendor portion has been agreed to be -pc- and it isn't
>>> -unknown-, a patch then should be created for config.guess to match the
>>> agreed upon vendor.  The config.guess script supplies the default to
>>> configure for the build and host.  The fact that config.guess supplies
>>> x86_64-unknown-cygwin is used by configure is the reason my assumptions
>>> are correct.  If -pc- should be used then config.guess needs to change.
>> Let us bring some sanity to this discussion/argument. With this repository:
>>    git clone --depth 1 git://github.com/php/php-src
>>    cd php-src
>>    ./buildconf
>> Test 1:
>>    $ ./configure --host x86_64-pc-cygwin
>>    checking build system type... x86_64-unknown-cygwin
>>    checking host system type... x86_64-pc-cygwin
>>    checking for x86_64-pc-cygwin-gcc... x86_64-pc-cygwin-gcc
>>    checking whether the C compiler works... yes
> Two things wrong with this:
> 1) If you specify --host, you need to specify --build as well.
> 2) If you're not cross-compiling or building a toolchain package, you
> shouldn't be specifying either.
>> Test 2:
>>    $ ./configure --host x86_64-unknown-cygwin
>>    checking build system type... x86_64-unknown-cygwin
>>    checking host system type... x86_64-unknown-cygwin
>>    checking for x86_64-unknown-cygwin-gcc... no
>>    checking for cc... cc
>>    checking whether the C compiler works... yes
>> So yes, specifying "--host x86_64-unknown-cygwin" causes it to not find
>> "x86_64-unknown-cygwin-gcc.exe", which makes sense because that doesnt
>> exist.
> True, when you *need* to specify --build/--host, then x86_64-pc-cygwin
> should be used.  When not (as in this case), then omit them.

So if autoconf does not find the triplet prefixed build tool, it should use the
non-triplet prefixed build tool, and if it doesn't do that, then there is an
issue either with the package autoconf setup or the autoconf package being used?

If that is the case with the OP's build, they should report it to the upstream
package maintainer.

-- 
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