From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Oleg Lyovin <ovlevin@sberdevices.ru>
Cc: olegartys@gmail.com, sdfw_system_team@sberdevices.ru,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/linux-headers: use host-make
Date: Fri, 7 Apr 2023 18:31:13 +0200 [thread overview]
Message-ID: <20230407183113.30ee6a87@windsurf> (raw)
In-Reply-To: <20230407141930.694756-1-ovlevin@sberdevices.ru>
Hello Oleg,
On Fri, 7 Apr 2023 17:19:29 +0300
Oleg Lyovin <ovlevin@sberdevices.ru> wrote:
> GNU make package from the host machine may be too old,
> so use the one built by buildroot.
>
> Signed-off-by: Oleg Lyovin <ovlevin@sberdevices.ru>
> ---
> package/linux-headers/linux-headers.mk | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
Thanks for the patch. However, could you provide some details on what
problem this is fixing? Is this due to something new in recent Linux
kernel releases that require a more recent version of make? If so, we
need to understand what is the Linux kernel change that causes that,
and what is the minimum make version that is now needed. Could you look
up those details?
Thanks a lot!
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
next prev parent reply other threads:[~2023-04-07 16:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 14:19 [Buildroot] [PATCH 1/2] package/linux-headers: use host-make Oleg Lyovin
2023-04-07 14:19 ` [Buildroot] [PATCH 2/2] linux: " Oleg Lyovin
2023-04-07 16:31 ` Thomas Petazzoni via buildroot [this message]
2023-04-10 7:46 ` [Buildroot] [PATCH 1/2] package/linux-headers: " Oleg Lyovin via buildroot
2023-04-10 15:24 ` Arnout Vandecappelle
2023-04-11 12:27 ` Peter Korsgaard
2023-04-11 13:01 ` Arnout Vandecappelle
2023-04-11 13:07 ` Peter Korsgaard
2023-04-11 13:14 ` David Laight
2023-04-11 13:26 ` Peter Korsgaard
2023-04-11 16:04 ` David Laight
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=20230407183113.30ee6a87@windsurf \
--to=buildroot@buildroot.org \
--cc=olegartys@gmail.com \
--cc=ovlevin@sberdevices.ru \
--cc=sdfw_system_team@sberdevices.ru \
--cc=thomas.petazzoni@bootlin.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