From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] intltool: add patch to fix compatibility with Perl 5.26
Date: Sun, 11 Jun 2017 15:52:28 +0200 [thread overview]
Message-ID: <20170611155228.6cda31e2@windsurf.home> (raw)
In-Reply-To: <20170608070344.30718-1-joerg.krause@embedded.rocks>
Hello,
On Thu, 8 Jun 2017 09:03:44 +0200, J?rg Krause wrote:
> When Perl 5.26 is installed on the host, building some packages like
> avahi fail, because of intltool-update:
>
> ```
> Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/^(.*)\${ <-- HERE ?([A-Z_]+)}?(.*)$/@$BUILDROOT/host/usr/bin/intltool-update line 1065.
> ```
>
> Apparently, this has been a warning before Perl 5.26, but now it is an
> error.
>
> Fetch from:
> https://github.com/Alexpux/MSYS2-packages/blob/master/intltool/perl-5.22-compatibility.patch
>
> Reported upstream:
> https://bugs.launchpad.net/intltool/+bug/1696658
>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> .../intltool/0001-perl-5.26-compatibility.patch | 53 ++++++++++++++++++++++
> 1 file changed, 53 insertions(+)
> create mode 100644 package/intltool/0001-perl-5.26-compatibility.patch
Applied to master, thanks.
FWIW, the bug was already reported upstream at
https://bugs.launchpad.net/intltool/+bug/1490906.
Peter: this is a build fix, we perhaps want it in the LTS branches?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-11 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 7:03 [Buildroot] [PATCH] intltool: add patch to fix compatibility with Perl 5.26 Jörg Krause
2017-06-11 13:52 ` Thomas Petazzoni [this message]
2017-06-13 21:13 ` Peter Korsgaard
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=20170611155228.6cda31e2@windsurf.home \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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