On 10/08/2022 11:35, Carlo B. wrote:
Il giorno mer 3 ago 2022 alle ore 21:52 Jon Turney
<jon.tur...@dronecode.org.uk> ha scritto:
On 22/07/2022 15:44, Carlo B. wrote:
it works, thank you very much.
I also added AUTOCONF_VERSION=2.13 directly into the cygport script,
before calling cygconf and it also worked fine without manually
setting that environment variable.
I think that it would be worth to update the cygport script into
autoconf2.1-2.13-12-src.tar.bz2 to make it working again also for
other people.
Is there something wrong with our supplied autconf2.1 package?
Nowadays, it is not possible to make the autconf2.1 package from "src"
because the errors written in previous emails.
I don't know if the fault is caused by a regression into cygport or it
is needed to fix the "src" package of autconf2.1 for supporting a new
syntax or something like that. Unfortunately, the main problem is that
running the cygport script for autoconf 2.1 still hangs, so perhaps it
would be useful to fix it, in one way or another one.
Thank you very much for your time and your reply.
This isn't really responsive to my question: Are you building an
autoconf2.1 package because the one we provide is deficient in some way,
or because you want to?
This is a regression in cygport, which I'll see about fixing.
This should be fixed as of cygport 0.35.3
(Briefly: cygport tries to detect the version of autoconf which was used
to generate the ./configure script, so it knows what option arguments to
supply to it. Recently this was extended to detect autoconf 2.7x, but
that seems to have broken detecting autoconf 2.1x)
--
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
