From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>,
Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/transmission: fix build with autoconf >= 2.71
Date: Sun, 10 Oct 2021 16:02:09 +0200 [thread overview]
Message-ID: <20211010160209.0955a1b3@windsurf> (raw)
In-Reply-To: <CAPi7W83-ZeLBacug7pzX=hjGz14RQEo1r-EjqDPkQ2YEitN8RA@mail.gmail.com>
Hello,
On Sat, 9 Oct 2021 23:01:54 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> > I am rather confused, because I don't see any changes between autoconf
> > 2.70 and 2.71 that seem to explain this, and the message "ERROR:
> > 'IT_PROG_INTLTOOL' must appear in configure.ac for intltool to work"
> I assume that the culprit on autoconf side is:
> http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commit;h=b3b3af821a0b9e82ebe56b77b1731d2fe58f52de
> So build failure is raised since autoconf 2.70 and not 2.71.
Ah, indeed that seems more plausible.
BTW, do you understand this mess of gtkdocize and intltoolize, and the
reasoning behind the commit that you're pointing to?
> A bug has been opened on intltool but there is no upstream reaction:
> https://bugs.launchpad.net/intltool/+bug/1921816
Yeah, I've seen that. And there has been no release since 2015
apparently.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-10 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 17:02 [Buildroot] [PATCH 1/1] package/transmission: fix build with autoconf >= 2.71 Fabrice Fontaine
2021-10-09 19:46 ` Thomas Petazzoni
2021-10-09 21:01 ` Fabrice Fontaine
2021-10-10 14:02 ` Thomas Petazzoni [this message]
2021-11-04 21:47 ` Thomas Petazzoni
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=20211010160209.0955a1b3@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=bernd.kuhls@t-online.de \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.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