public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "Carlo B." <carlo.bramini@gmail.com>,
	The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Error when building autoconf2.1, broken package?
Date: Wed, 3 Aug 2022 20:52:06 +0100	[thread overview]
Message-ID: <de8f1bd6-8d7f-792a-6074-abfa3e655c8d@dronecode.org.uk> (raw)
In-Reply-To: <CADt9574Yo=BRc26A4FdGucoEOjXV+kRsJ3BrDCzLSaejU_r+pQ@mail.gmail.com>

On 22/07/2022 15:44, Carlo B. wrote:
> Hello,
> 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?

> 
> Sincerely,
> 
> Carlo Bramini.
> 
> Il giorno gio 21 lug 2022 alle ore 15:07 Takashi Yano
> <takashi.yano@nifty.ne.jp> ha scritto:
>>
>> On Tue, 19 Jul 2022 12:42:47 +0200
>> "Carlo B." wrote:
>>> Hello,
>>> I did these actions:
>>> 1) Downloaded autoconf2.1-2.13-12-src.tar.bz2
>>> 2) Unpack that file.
>>> 3) I run this command:
>>>
>>> cygport autoconf2.1.cygport all
>>>
>>> and this is the output on screen:
>>>
>>>>>> Preparing autoconf2.1-2.13-12.x86_64
>>>>>> Unpacking source autoconf-2.13.tar.gz
>>> *** Info: applying patch autoconf2.1-texinfo.patch (-p2):
>>> patching file autoconf.texi
>>>>>> Preparing working source directory
>>> *** Info: applying patch autoconf2.1-2.13-12.cygwin.patch (-p2):
>>> patching file CYGWIN-PATCHES/autoconf2.1.README
>>>>>> Compiling autoconf2.1-2.13-12.x86_64
>>> *** ERROR: could not detect autoconf version; perhaps set AUTOCONF_VERSION?

This is a regression in cygport, which I'll see about fixing.

(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)

>>>
>>> Have you an idea of the cause of the problem?
>>> I tried to download and rebuild also autoconf2.5 and autoconf2.7 and
>>> they worked fine, only 2.1 fails.
>>> Thank you very much for your time.
>>
>> I could build autoconf2.1 successfully by the following steps.
>>
>>
>> 1) Modify autoconf2.1.cygport as follows.
>>
>> diff --git a/autoconf2.1.cygport.orig b/autoconf2.1.cygport
>> index c8b075f..6876c3c 100755
>> --- a/autoconf2.1.cygport.orig
>> +++ b/autoconf2.1.cygport
>> @@ -28,7 +28,7 @@ src_compile() {
>>          cd ${B}
>>          cygconf --program-suffix=-2.13
>>          cygmake -j1
>> -       (makeinfo --no-split -I ${S} -o autoconf2.13.info autoconf.texi)
>> +       (makeinfo --no-split -o autoconf2.13.info ${S}/autoconf.texi)

I'm not sure why this change is needed.

>>   }
>>
>>   DIFF_EXCLUDES="autoconf.info standards.info stamp-vti version.texi"
>>
>> 2) Run 'export AUTOCONF_VERSION=2.13'
>> 3) Run 'cygport autoconf2.1.cygport all'

  reply	other threads:[~2022-08-03 19:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 10:42 Carlo B.
2022-07-21 13:06 ` Takashi Yano
2022-07-22 14:44   ` Carlo B.
2022-08-03 19:52     ` Jon Turney [this message]
2022-08-10 10:35       ` Carlo B.
2022-09-30 13:25         ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=de8f1bd6-8d7f-792a-6074-abfa3e655c8d@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=carlo.bramini@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).