On 31/08/2025 18:18, ASSI via Cygwin wrote:
Christian Franke via Cygwin writes:
The cygport scripts from various automake packages run 'gnuconfigize'
which overwrite the upstream versions of config.guess and config.sub
with the now 5+ year old versions provided by cygport.
$ cygcheck -f /usr/share/automake-1.18/config.guess
automake1.18-1.18.1-1
$ cygcheck -f /usr/share/cygport/config.guess
cygport-0.37.2-1
$ md5sum /usr/share/automake-1.*/config.guess
/usr/share/cygport/config.guess
cc0f5d60f7505c777959126329bcaca6 */usr/share/automake-1.10/config.guess
559bc9e2fca45761389ce2f3140cec0c */usr/share/automake-1.11/config.guess
d9375ba9d0b8cfd7bb6737e3fc43984f */usr/share/automake-1.12/config.guess
eea34cf893bb060ee20189e256a8065a */usr/share/automake-1.13/config.guess
467fb07b9fc0b8cf59750c8ca8b3f7d5 */usr/share/automake-1.14/config.guess
467fb07b9fc0b8cf59750c8ca8b3f7d5 */usr/share/automake-1.15/config.guess
467fb07b9fc0b8cf59750c8ca8b3f7d5 */usr/share/automake-1.16/config.guess
467fb07b9fc0b8cf59750c8ca8b3f7d5 */usr/share/automake-1.17/config.guess
467fb07b9fc0b8cf59750c8ca8b3f7d5 */usr/share/automake-1.18/config.guess
467fb07b9fc0b8cf59750c8ca8b3f7d5 */usr/share/cygport/config.guess
$ # ... same for config.sub ...
$ grep ^timestamp /usr/share/cygport/config.*
/usr/share/cygport/config.guess:timestamp='2020-04-26'
/usr/share/cygport/config.sub:timestamp='2020-05-04'
Upstream:
automake-1.18.1/lib/config.sub:timestamp='2024-05-27'
Is this downgrade intentional?
Well, Yaakov obviously did that for some reason that is not really
transparent to me now and started doing so much earlier than the version
of the current file suggests (at leat in 2014). From the comments, what
he wanted to do is keep a newer version that made it into cygport via a
submodule in data/gnuconfig… which has never been updated since Yaakov
dropped maintenance, most likely because that wasn't really on the radar
until now. Now, I could certainly rip out the gnuconfigize from the
autotools packages 1.16+ since these would all come with later versions
of these files, but I have no idea what secondary effects this will
have.
Yeah, this all lines up with me taking over as maintainer and not
realizing these needed keeping up to date.
I've added an action to my release checklist for cygport, so hopefully
this won't be an issue in future...
--
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
