From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13141] Target-finalize fail with "depmod: ERROR: Bad version passed"
Date: Tue, 25 Aug 2020 05:43:44 +0000 [thread overview]
Message-ID: <bug-13141-163-3GVXm5VRdU@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13141-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13141
--- Comment #4 from laurent at neko-labs.eu ---
(In reply to Asaf Kahlon from comment #2)
Asaf, Yann,
1/As suggested by asaf I checked my build script and I had:
make -C $BR_SOURCE O=$BR_BUILD -j`nproc` V=1
Removing -j`nproc` seems to remove the issue.
--> I did the test during the night, I'll recheck tonight to be sure.
2/Asaf you are right first time I build it failed (with -j`nproc`), then next
time it succeed, but I was suspecting that buildroot somehow .stamp'ed the
TARGET_FINALIZE stage.
Laurent
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-08-25 5:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 22:03 [Buildroot] [Bug 13141] New: Target-finalize fail with "depmod: ERROR: Bad version passed" bugzilla at busybox.net
2020-08-23 22:09 ` [Buildroot] [Bug 13141] " 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 [this message]
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-3GVXm5VRdU@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