From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13141] New: Target-finalize fail with "depmod: ERROR: Bad version passed"
Date: Thu, 06 Aug 2020 22:03:27 +0000 [thread overview]
Message-ID: <bug-13141-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13141
Bug ID: 13141
Summary: Target-finalize fail with "depmod: ERROR: Bad version
passed"
Product: buildroot
Version: 2020.02.1
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: laurent at neko-labs.eu
CC: buildroot at uclibc.org
Target Milestone: ---
Hello,
I've successfully build my system up to 2020.02.
But when I started to try to build 2020.02.1 and onwards it always failed with
"depmod: ERROR: Bad version passed" message during TARGET_FINALIZE step.
I managed to find the commit that make my build fail:
8f5a610fe81676092a6960415717de731f43f8bf
linux: Allow modprobe for out-of-tree modules
When LINUX_TARGET_FINALIZE_HOOKS are call the new LINUX_RUN_DEPMOD function
fail in my case.
# Run depmod in a target-finalize hook, to encompass modules installed by
# packages.
define LINUX_RUN_DEPMOD
$(HOST_DIR)/sbin/depmod -a -b $(TARGET_DIR) $(LINUX_VERSION_PROBED)
endef
LINUX_TARGET_FINALIZE_HOOKS += LINUX_RUN_DEPMOD
Here is my $(LINUX_VERSION_PROBED): 4.19.78-linux4sam-6.2
I'm using a buildroot external tree for my board, still I've attached my
.config file if it can help
What I don't understand is that if I run manually the depmod command it pass
successfully :/
---> builroot log:
/home/buildroot/output/host/sbin/depmod -a -b /home/buildroot/output/target
`/usr/bin/make HOSTCC="/home/buildroot/output/host/bin/ccache /usr/bin/gcc -O2
-I/home/buildroot/output/host/include -L/home/buildroot/output/host/lib
-Wl,-rpath,/home/buildroot/output/host/lib" ARCH=arm
INSTALL_MOD_PATH=/home/buildroot/output/target
CROSS_COMPILE="/home/buildroot/output/host/bin/arm-buildroot-linux-gnueabihf-"
DEPMOD=/home/buildroot/output/host/sbin/depmod INSTALL_MOD_STRIP=1 -C
/home/buildroot/output/build/linux-linux4sam_6.2 --no-print-directory -s
kernelrelease 2>/dev/null`
depmod: ERROR: Bad version passed make[1]:
make: *** [Makefile:747: target-finalize] Error 1
---> My manual commands (that succeed):
#/usr/bin/make HOSTCC="/home/buildroot/output/host/bin/ccache /usr/bin/gcc -O2
-I/home/buildroot/output/host/include -L/home/buildroot/output/host/lib
-Wl,-rpath,/home/buildroot/output/host/lib" ARCH=arm
INSTALL_MOD_PATH=/home/buildroot/output/target
CROSS_COMPILE="/home/buildroot/output/host/bin/arm-buildroot-linux-gnueabihf-"
DEPMOD=/home/buildroot/output/host/sbin/depmod INSTALL_MOD_STRIP=1 -C
/home/buildroot/output/build/linux-linux4sam_6.2 --no-print-directory -s
kernelrelease 2>/dev/null
4.19.78-linux4sam-6.2
#/home/buildroot/output/host/sbin/depmod -a -b /home/buildroot/output/target
4.19.78-linux4sam-6.2
OK
Any help appreciated!
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-08-06 22:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 22:03 bugzilla at busybox.net [this message]
2020-08-23 22:09 ` [Buildroot] [Bug 13141] Target-finalize fail with "depmod: ERROR: Bad version passed" bugzilla at busybox.net
2020-08-24 5:00 ` bugzilla at busybox.net
2020-08-24 23:33 ` bugzilla at busybox.net
2020-08-25 5:43 ` bugzilla at busybox.net
2020-08-25 7:35 ` bugzilla at busybox.net
2020-08-25 14:30 ` bugzilla at busybox.net
2020-08-25 15:43 ` bugzilla at busybox.net
2020-08-25 18:57 ` bugzilla at busybox.net
2020-08-25 19:29 ` bugzilla at busybox.net
2020-08-28 21:06 ` bugzilla at busybox.net
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=bug-13141-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox