From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Sergey Bobrenok <sibobrenok@salutedevices.com>
Cc: Sergey Bobrenok <SIBobrenok@sberdevices.ru>,
Alexey Romanov <avromanov@sberdevices.ru>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/pkg-kernel-module: add BR2_MAKE_HOST_DEPENDENCY
Date: Tue, 24 Oct 2023 21:23:06 +0200 [thread overview]
Message-ID: <20231024192306.GC2607@scaer> (raw)
In-Reply-To: <20231024153023.19173-1-sibobrenok@salutedevices.com>
Sergey, All,
On 2023-10-24 18:30 +0300, Sergey Bobrenok via buildroot spake thusly:
> From: Alexey Romanov <avromanov@sberdevices.ru>
>
> Commit 0b9efc991f ("linux: use BR2_MAKE") switched LINUX_MAKE to
> $(BR2_MAKE) to avoid build issue with kernel version >= 6.2 and GNU
> Make version < 3.82. However, the same issue is actual for kernel
> modules as well.
>
> Using $(BR2_MAKE) should guarantee a consistent behavior between
> kernel and kernel-modules builds.
>
> Signed-off-by: Alexey Romanov <avromanov@sberdevices.ru>
> Signed-off-by: Sergey Bobrenok <SIBobrenok@sberdevices.ru>
> ---
> package/pkg-kernel-module.mk | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/package/pkg-kernel-module.mk b/package/pkg-kernel-module.mk
> index fcd6b8bc29..ae7a09114e 100644
> --- a/package/pkg-kernel-module.mk
> +++ b/package/pkg-kernel-module.mk
> @@ -50,11 +50,12 @@ LINUX_NEEDS_MODULES = y
> endif
>
> # The kernel must be built first.
> -$(2)_DEPENDENCIES += linux
> +$(2)_DEPENDENCIES += linux \
> + $$(BR2_MAKE_HOST_DEPENDENCY)
With multi-line assignments, each value should be on its own line. Also,
indentation should be with TAB, not spaces.
Applied to master with the above fixed, thanks.
Regards,
Yann E. MORIN.
> # This is only defined in some infrastructures (e.g. autotools, cmake),
> # but not in others (e.g. generic). So define it here as well.
> -$(2)_MAKE ?= $$(MAKE)
> +$(2)_MAKE ?= $$(BR2_MAKE)
>
> # If not specified, consider the source of the kernel module to be at
> # the root of the package.
> --
> 2.24.3 (Apple Git-128)
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-10-24 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 15:30 [Buildroot] [PATCH 1/1] package/pkg-kernel-module: add BR2_MAKE_HOST_DEPENDENCY Sergey Bobrenok via buildroot
2023-10-24 19:23 ` Yann E. MORIN [this message]
2023-10-30 10: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=20231024192306.GC2607@scaer \
--to=yann.morin.1998@free.fr \
--cc=SIBobrenok@sberdevices.ru \
--cc=avromanov@sberdevices.ru \
--cc=buildroot@buildroot.org \
--cc=sibobrenok@salutedevices.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