DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:subject:to:references
	:content-type; q=dns; s=default; b=HK0Ramz76LUSgtELjpzhpRgUvAuuD
	YPagwJdHCli/nCVsHVkq8BV2M2d+1fFUM2eOg/wOE9Iq31feI0Go0XB++VNVW7OK
	W1tJm+1KEVKvSLB3hR98pKka+Sv0ECGnHrfrxeytGWkPHaa1Lp8A2riHKMqEDekl
	lcvesEeauCcqo4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <59e939fc.21539d0a.6c79e.530e@mx.google.com>
Date: Thu, 19 Oct 2017 16:49:16 -0700 (PDT)
From: Steven Penny <svnpenn AT gmail DOT com>
Subject: Re: Which is it -pc- or -unknown-
To: cygwin AT cygwin DOT com
References: <a9cce58b-13c4-510e-e93a-188ac407d95c AT gmail DOT com>
Content-Type: text/plain; charset=utf8; format=flowed
User-Agent: Tryst/2.0.1 (github.com/svnpenn/tryst)

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

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.
However notice carefully in the next step that it finds
"x86_64-pc-cygwin-gcc.exe:

    $ ls -l /bin/cc
    lrwxrwxrwx 1 Steven None 7 Sep  9 17:18 /bin/cc -> gcc.exe

    $ find /bin -samefile /bin/gcc
    /bin/gcc.exe
    /bin/x86_64-pc-cygwin-gcc-6.4.0.exe
    /bin/x86_64-pc-cygwin-gcc.exe


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