From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] package/openrc: adapt "modules" init script to busybox "modprobe"
Date: Thu, 27 Feb 2020 18:27:27 +0100 [thread overview]
Message-ID: <20200227182727.0b277df7@windsurf> (raw)
In-Reply-To: <20200227123938.13412-4-unixmania@gmail.com>
On Thu, 27 Feb 2020 09:39:37 -0300
unixmania at gmail.com wrote:
> +# modprobe can be provided by either kmod or busybox
> +ifeq ($(BR2_PACKAGE_KMOD_TOOLS),)
> +ifeq ($(BR2_PACKAGE_BUSYBOX),y)
> +# Busybox modprobe does not have a --first-time option; --verbose is just -v
> +# and --use-blacklist is just -b.
> +ifeq ($(call KCONFIG_GET_OPT,CONFIG_MODPROBE,$(BUSYBOX_BUILD_CONFIG)),y)
Is this working? Isn't that evaluated when Makefiles are parsed, i.e
before the build has extracted Busybox and created its .config file ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-27 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 12:39 [Buildroot] [PATCH 0/4] adapt openrc "modules" script to busybox modprobe unixmania at gmail.com
2020-02-27 12:39 ` [Buildroot] [PATCH 1/4] Makefile: add SED_QUIET unixmania at gmail.com
2020-02-27 12:39 ` [Buildroot] [PATCH 2/4] package/pkg-utils.mk: add KCONFIG_GET_OPT macro unixmania at gmail.com
2020-02-27 12:39 ` [Buildroot] [PATCH 3/4] package/openrc: adapt "modules" init script to busybox "modprobe" unixmania at gmail.com
2020-02-27 17:27 ` Thomas Petazzoni [this message]
2020-02-27 18:57 ` Carlos Santos
2020-02-27 20:16 ` Carlos Santos
2020-02-27 12:39 ` [Buildroot] [PATCH 4/4] package/busybox: document the use of BUSYBOX_BUILD_CONFIG in openrc.mk unixmania at gmail.com
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=20200227182727.0b277df7@windsurf \
--to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.