Web lists-archives.com

Re: Which is it -pc- or -unknown-

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