From: Li Chen<me@linux.beauty>
To: buildroot@buildroot.org
Cc: Li Chen <me@linux.beauty>
Subject: [Buildroot] [PATCH] package/kmod: use the correct path for kmod
Date: Wed, 12 Oct 2022 09:34:39 +0800 [thread overview]
Message-ID: <87edvdeseo.wl-me@linux.beauty> (raw)
Content-Transfer-Encoding: 8bit
kmod install path is always /usr/bin/kmod instead
of /bin/kmod.
So if we link modprobe/lsmod/... to /bin/kmod
We will get error like:
> # modprobe
> -sh: modprobe: not found
because it points to:
> # ls -liah /sbin/modprobe
> 2551 lrwxrwxrwx 1 root root 11 Sep 25 10:05 /sbin/modprobe -> ../bin/kmod
and kmod is under /usr/bin/kmod instead of /bin/kmod.
Signed-off-by: Li Chen <me@linux.beauty>
---
package/kmod/kmod.mk | 5 -----
1 file changed, 5 deletions(-)
diff --git a/package/kmod/kmod.mk b/package/kmod/kmod.mk
index 82e8597759..cfb4a27cf3 100644
--- a/package/kmod/kmod.mk
+++ b/package/kmod/kmod.mk
@@ -73,12 +73,7 @@ ifeq ($(BR2_PACKAGE_KMOD_TOOLS),y)
KMOD_LICENSE += , GPL-2.0+ (tools)
KMOD_LICENSE_FILES += COPYING
-# /sbin is really /usr/sbin with merged /usr, so adjust relative symlink
-ifeq ($(BR2_ROOTFS_MERGED_USR),y)
-KMOD_BIN_PATH = ../bin/kmod
-else
KMOD_BIN_PATH = ../usr/bin/kmod
-endif
define KMOD_INSTALL_TOOLS
for i in depmod insmod lsmod modinfo modprobe rmmod; do \
--
2.37.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-10-12 1:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 1:34 Li Chen [this message]
2022-10-12 20:40 ` [Buildroot] [PATCH] package/kmod: use the correct path for kmod Thomas Petazzoni via buildroot
2022-10-16 4:08 ` Li Chen
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=87edvdeseo.wl-me@linux.beauty \
--to=me@linux.beauty \
--cc=buildroot@buildroot.org \
/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