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
