DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:reply-to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=g9nB86XJcUp0gJKC
	6WP5eMj7DWswMOTqJ4/hnfWH3Tuw0eUoUbnSSphCvBSCsYdRUH4qMx/8kbwfl8wY
	QgG0rRDbrz2Qm/79Gt20wcUDvE+0DGXLe5ql8Q9VitNBUBfkRPLua2oYVFJDrog6
	PhG/lSL6NpBtXa9EcwsHrowyKfQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Which is it -pc- or -unknown-
To: cygwin@cygwin.com
References: <7983d97c-3c6d-e3c2-2304-9527ad4c5735@gmail.com> <59e8f0cd.28279d0a.292b.4768@mx.google.com> <e3abcc71-e085-4355-41de-c6ab30cc4c85@gmail.com> <8a790ade-1761-b87b-b389-5f76d147c099@cygwin.com> <217068b0-f4df-1c30-07f7-8d7cbf84a52a@SystematicSw.ab.ca> <f499654d-44d0-6b06-6add-ce77ad16d5f4@gmail.com> <d4235ee2-1767-15d7-8a2f-11e93a0ecdb3@cygwin.com>
From: cyg Simple <cygsimple@gmail.com>
Reply-To: cygwin@cygwin.com
Message-ID: <a9cce58b-13c4-510e-e93a-188ac407d95c@gmail.com>
Date: Thu, 19 Oct 2017 17:00:12 -0400
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: <d4235ee2-1767-15d7-8a2f-11e93a0ecdb3@cygwin.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit

On 10/19/2017 4:35 PM, Yaakov Selkowitz wrote:
> On 2017-10-19 15:02, cyg Simple wrote:
>> On 10/19/2017 3:54 PM, Brian Inglis wrote:
>>> On 2017-10-19 12:59, Yaakov Selkowitz wrote:
>>>> On 2017-10-19 13:40, cyg Simple wrote:
>>>>> x86_64-pc-cygwin is just not correct regardless of the lack of past issues.
>>>>
>>>> As I have said several times, this assertion is incorrect.  You need to
>>>> use the triplet which matches the toolchain with which you are building.
>>>> For example, Fedora and RHEL all use $arch-redhat-linux as their
>>>> triplet, and there is nothing wrong with that.
>>>
>>> Vendor -unknown- is just a default in various config cases, so specifying -pc-
>>> for consistency on Cygwin builds is a valid choice by the maintainers.
>>
>> FINE!  But config.guess should match the CHOSEN one.
> 
> Incorrect assumption.
> 

You keep saying my assumption is incorrect but that isn't the case.  My
assumption is based on data supplied by the configure process.

>>> Perhaps a statement on the cygwin-apps list could clarify what should be done by
>>> maintainers to ensure this override, and maybe retire the use of -unknown- by
>>> any Cygwin apps in future, with a notice to this (cygwin) list for those who
>>> choose to build packages from net sources.
>>
>> I don't care which is used as long as config.guess matches what is chosen.
> 
> That is not a requirement.
> 
>>> Perhaps also patches should be submitted to the config and automake maintainers
>>> to ensure that {i*,x86_64}:CYGWIN*:*... always produce vendor -pc-. Not sure
>>> about vendors for {amd64,powerpcle}:CYGWIN*:*... in config.guess, which are
>>> currently also set to -unknown-.
>>
>> Exactly what I'm saying.  It needs to match what is being distributed
>> just for consistency and to avoid confusion.
> 
> No patch is needed here.

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.

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