matthew patton via Cygwin wrote:
has anyone diff'd the 'custom' one vs the standard to see if there any actionable
differences? Or was this a "temporary" bodge that was never backed out once
upstream became usable?
$ cygport automake1.18.cygport prep make
...
$ diff -r automake1.18-1.18.1-1.noarch/{orig,}src | diffstat
CYGWIN-PATCHES |only
lib/config.guess | 1269 +++++++++++++++++++-------------------------
lib/config.sub | 1423 +++++++++++++++-----------------------------------
3 files changed, 995 insertions(+), 1697 deletions(-)
The observation that leaded to the investigation was a 'host'
misdetection under "ubuntu-latest" (automake 1.16.5) from GH Actions:
$ ./configure "CC=gcc -m32" # AC_CANONICAL_HOST sets 'host' to
x86_64-pc-linux-gnu # Cygwin automake 1.14-1.18
x86_64-pc-linux-gnux32 # ("x86_64 with x32 ABI") automake 1.16.5
i686-pc-linux-gnu # automake >= 1.17
On Cygwin, x86_64-pc-cygwin is correctly detected in all cases.
--
Regards,
Christian
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
