From: Ladislav Michl <oss-lists@triops.cz>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [RFC] Do not select INITMETHOD
Date: Wed, 4 Jan 2023 15:47:43 +0100 [thread overview]
Message-ID: <Y7WRjwb6WsAE0z9A@lenoch> (raw)
Do not force INITMETHOD to allow BSPs to use alternative inits
on their own (minit for example)
Now that initmethod.in part of patch is questionable, but it breaks
various ways without it, for example:
WARNING: unmet direct dependencies detected for RC_ONCE
Depends on [n]: INITMETHOD [=n]
Selected by [m]:
- DROPBEAR [=m] && RUNTIME [=y]
Any other ideas?
Thak you,
ladis
---
rules/dropbear.in | 1 -
rules/initmethod.in | 4 ++--
rules/lldpd.in | 1 -
3 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/rules/dropbear.in b/rules/dropbear.in
index 95beb09bf..7b5736696 100644
--- a/rules/dropbear.in
+++ b/rules/dropbear.in
@@ -6,7 +6,6 @@ menuconfig DROPBEAR
select LIBC_UTIL
select LIBC_CRYPT
select GCCLIBS_GCC_S
- select INITMETHOD
select RC_ONCE if RUNTIME
select BUSYBOX_START_STOP_DAEMON if DROPBEAR_STARTSCRIPT
select BUSYBOX_FEATURE_START_STOP_DAEMON_FANCY if DROPBEAR_STARTSCRIPT
diff --git a/rules/initmethod.in b/rules/initmethod.in
index 489fd365d..4066a05ba 100644
--- a/rules/initmethod.in
+++ b/rules/initmethod.in
@@ -33,6 +33,6 @@ choice
endchoice
-source "generated/initmethod.in"
-
endif
+
+source "generated/initmethod.in"
diff --git a/rules/lldpd.in b/rules/lldpd.in
index 8b253ba83..d2afccbd0 100644
--- a/rules/lldpd.in
+++ b/rules/lldpd.in
@@ -3,7 +3,6 @@
menuconfig LLDPD
tristate
prompt "lldpd "
- select INITMETHOD
select LIBBSD
select LIBCAP
select LIBEVENT
--
2.32.0
next reply other threads:[~2023-01-04 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 14:47 Ladislav Michl [this message]
2023-01-05 7:26 ` Michael Olbrich
2024-08-26 6:53 ` Ladislav Michl
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=Y7WRjwb6WsAE0z9A@lenoch \
--to=oss-lists@triops.cz \
--cc=ptxdist@pengutronix.de \
/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