From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/transmission: fix build with autoconf >= 2.71
Date: Thu, 4 Nov 2021 22:47:21 +0100 [thread overview]
Message-ID: <20211104224721.79b7c232@windsurf> (raw)
In-Reply-To: <20211009170242.486738-1-fontaine.fabrice@gmail.com>
On Sat, 9 Oct 2021 19:02:42 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following build failure raised since bump of autoconf to version
> 2.71 in commit ecd54b65c1f998a7ccd91f7c523e4ff38c4781da:
>
> ERROR: 'IT_PROG_INTLTOOL' must appear in configure.ac for intltool to work.
>
> Fixes:
> - http://autobuild.buildroot.org/results/e8bea26f6b12adf16335b24836a7c5c31911af6a
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...ac-fix-autoreconf-with-autoconf-2.71.patch | 39 +++++++++++++++++++
> 1 file changed, 39 insertions(+)
> create mode 100644 package/transmission/0003-configure.ac-fix-autoreconf-with-autoconf-2.71.patch
I've applied to master after adjusting the patch and commit log to
indicate the issue is with autoconf 2.70, not 2.71. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-11-04 21:47 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
2021-11-04 21:47 ` Thomas Petazzoni [this message]
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=20211104224721.79b7c232@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