From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] linux: add conditional patch for timeconst.pl
Date: Wed, 10 Feb 2016 00:08:58 +0100 [thread overview]
Message-ID: <56BA718A.5060500@mind.be> (raw)
In-Reply-To: <1454852508-27544-1-git-send-email-gustavo.zacarias@free-electrons.com>
On 07-02-16 14:41, gustavo.zacarias at free-electrons.com wrote:
> From: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
>
> Kernels older than 3.9 (not counting stable releases) used the
> timeconst.pl perl script for their build process.
> The problem with this script is that it used deprecated perl features,
> namely defined(@array) which was removed for the perl 5.22 release,
> causing build failure of older kernels on newer distributions.
>
> To fix this instead of going the hard way (moving to the new
> timeconst.bc script) use the easy way by patching timeconst.pl with an
> upstream patch used for stable releases.
>
> First try a dry-run on the patch to see if it applies, if it does then
> call a proper APPLY_PATCHES to it.
>
> Tested against an arbitrary 2.6.30 kernel (applies and builds), against
> 4.4.1 for a missing timeconst.pl (does not apply since it's missing) and
> 3.8.13 (does not apply since it's fixed already).
>
> Known broken distributions: fedora 23.
and debian testing (stretch) and unstable (sid).
As Thomas said, it's dirty, but we really need this.
>
> Signed-off-by: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
> ---
> v2: rebase on top of master
>
> ...nst.pl-Eliminate-Perl-warning.patch.conditional | 45 ++++++++++++++++++++++
> linux/linux.mk | 10 +++++
> 2 files changed, 55 insertions(+)
> create mode 100644 linux/0001-timeconst.pl-Eliminate-Perl-warning.patch.conditional
>
[snip]
> diff --git a/linux/linux.mk b/linux/linux.mk
> index 578fea1..7e20255 100644
> --- a/linux/linux.mk
> +++ b/linux/linux.mk
> @@ -184,6 +184,16 @@ endef
>
> LINUX_POST_PATCH_HOOKS += LINUX_APPLY_LOCAL_PATCHES
>
> +# Older linux kernels use deprecated perl constructs in timeconst.pl
> +# that were removed for perl 5.22+ so it breaks on newer distributions
> +# Try a dry-run patch to see if this applies, if it does go ahead
> +define LINUX_TRY_PATCH_TIMECONST
> + @if patch -p1 --dry-run -f -s -d $(@D) <$(LINUX_PKGDIR)/0001-timeconst.pl-Eliminate-Perl-warning.patch.conditional >/dev/null ; then \
> + $(APPLY_PATCHES) $(@D) $(LINUX_PKGDIR) 0001-timeconst.pl-Eliminate-Perl-warning.patch.conditional ; \
The only reason to use APPLY_PATCHES is that it updates .applied_patches_list,
right? In that case, perhaps it's better to do that directly here. So instead of
a dry-run, just apply the patch right away, and if it succeeds add it to
.applied_patches_list.
> + fi
> +endef
> +LINUX_POST_PATCH_HOOKS += LINUX_TRY_PATCH_TIMECONST
This is a patch that we probably _do_ want to apply even in case of
OVERRIDE_SRCDIR. So maybe add it to LINUX_PRE_CONFIGURE_HOOKS instead. Even
though that's even more of a hack (and conflicts with the out-of-tree build
support).
Regards,
Arnout
> +
> ifeq ($(BR2_LINUX_KERNEL_USE_DEFCONFIG),y)
> LINUX_KCONFIG_DEFCONFIG = $(call qstrip,$(BR2_LINUX_KERNEL_DEFCONFIG))_defconfig
> else ifeq ($(BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG),y)
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-02-09 23:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 13:41 [Buildroot] [PATCH v2] linux: add conditional patch for timeconst.pl gustavo.zacarias at free-electrons.com
2016-02-07 14:50 ` Thomas Petazzoni
2016-02-09 23:08 ` Arnout Vandecappelle [this message]
2016-02-09 23:19 ` Gustavo Zacarias
2016-02-10 0:37 ` Arnout Vandecappelle
2016-02-10 1:27 ` Gustavo Zacarias
2016-02-10 7:11 ` Peter Korsgaard
2016-02-10 7:12 ` 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=56BA718A.5060500@mind.be \
--to=arnout@mind.be \
--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