delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2017/10/19/19:49:32

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:message-id:date:from:subject:to:references
:content-type; q=dns; s=default; b=HK0Ramz76LUSgtELjpzhpRgUvAuuD
YPagwJdHCli/nCVsHVkq8BV2M2d+1fFUM2eOg/wOE9Iq31feI0Go0XB++VNVW7OK
W1tJm+1KEVKvSLB3hR98pKka+Sv0ECGnHrfrxeytGWkPHaa1Lp8A2riHKMqEDekl
lcvesEeauCcqo4=
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:message-id:date:from:subject:to:references
:content-type; s=default; bh=xoXNFq4UOssriVgdoShdhqi3rAw=; b=QuZ
D1mJNC1HumMdpLChLkHE/JkghkI1nrpuOH+0tgLIkVumgcoqEYiRg3T/tAsR/FLL
42fwn+FmKmy4Aw0/g4OxBStzwTy0dK2Oq99Enk106PLFLm90hFMRQXqjlIY6UQWu
wJxVrL3SrB8EhfgcxiKNRoBUMLX+hHF88mfiJrLg=
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.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=H*c:utf8, H*UA:github.com, H*M:google, you!
X-HELO: mail-oi0-f46.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:subject:to:references :user-agent; bh=TBkmg0xqeLg2sDBwflO9dCx9fC0Bj63XeJwDRjzzsow=; b=CeAvahHp8gfruNT+EhUoCNZCzzkkmEMgHW65mGgfVQOBK7enZNTkyrKoxPjOAyMu83 RGInuLV4/bBuGaZjP4nPac5eV/+9t2JjaBxH0UstW2FJsaTUq27wcM4+BG7SbZGJynRr EjhKi/DbggzP/ICI1u2kNoMLizQgEo38aPOEsWNcKQsuX4KSWXmTf6ndjkf8aW0lPV8n +NaFMUBsrGprnCVxW+7eWbUPf14G7oPW7/+3SerYpDi5NHS/0wHhh9dIX4rkxSiPIRcS Hgp833wZLNahdbcM/FdSDWk09FpGtknYt0czGvSZvrJQDBYQG4Fu4M7kSv8l64GZMDIN yeTg==
X-Gm-Message-State: AMCzsaWVFc0Vi40KZwFrXP01fm0Bw48UTw5dBYPxnf5gGFn1wIS8e5AI wUWi/Pq/bNe76eG/hjagGRS16g==
X-Google-Smtp-Source: ABhQp+S1fO7EMXKSg9p4YiPwTPC1/Nv2+ag++0lbGNvHxRu01iYBNY82Msscgxtd0XgMo/Q1VkUMkA==
X-Received: by 10.157.17.80 with SMTP id p16mr1861215otp.371.1508456956844; Thu, 19 Oct 2017 16:49:16 -0700 (PDT)
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>
X-Google-Original-From: Steven Penny
Subject: Re: Which is it -pc- or -unknown-
To: cygwin AT cygwin DOT com
References: <a9cce58b-13c4-510e-e93a-188ac407d95c AT gmail DOT com>
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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019