Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 1/1] board/wandboard: fix perl related linux compilation error
Date: Tue, 22 Sep 2015 15:47:16 +0200	[thread overview]
Message-ID: <20150922154716.0c3fec44@free-electrons.com> (raw)
In-Reply-To: <1442889921-6713-1-git-send-email-imrehg@gmail.com>

Hello,

On Tue, 22 Sep 2015 10:45:21 +0800, imrehg at gmail.com wrote:
> From: Gergely Imreh <imrehg@gmail.com>
> 
> Replace the "timeconst" perl script with a bc script to fix an
> error due to syntax changes in perl which resulted in linux
> compilation error for the wandboard's 3.8 kernel. The patch is
> backported, kernels from 3.9 onward already have this change.
> 
> Signed-off-by: Gergely Imreh <imrehg@gmail.com>

The problem with this patch is that it fixes the problem specifically
for the wandboard_defconfig. Any other person building another kernel
version affected by the same problem will face the problem.

If the problem is serious, I don't really see another option than
having some logic in linux.mk to detect if the kernel is affected by
the problem, and replacing the perl script by a bc script.

Other ideas?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-09-22 13:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22  2:45 [Buildroot] [PATCHv2 1/1] board/wandboard: fix perl related linux compilation error imrehg at gmail.com
2015-09-22 13:47 ` Thomas Petazzoni [this message]
2015-09-23 15:26   ` Gergely Imreh
2015-10-03 19:08   ` Peter Korsgaard
2015-10-03 20:48     ` Peter Korsgaard
2015-10-03 21:06       ` Arnout Vandecappelle
2015-10-03 21:19         ` Peter Korsgaard
2016-03-08 16:22 ` 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=20150922154716.0c3fec44@free-electrons.com \
    --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