From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Budi <budikusasi@gmail.com>, linux-kernel@vger.kernel.org
Cc: Linux Kernel Build System <linux-kbuild@vger.kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: Anyone please do big favor, help
Date: Tue, 4 Jul 2023 11:01:56 +0700 [thread overview]
Message-ID: <ZKOZtP72vmF8d6yi@debian.me> (raw)
In-Reply-To: <CAH0GyZDWhSo+otkEPRDwvHyE29N5ZjhpFT5m4jRnt6buV8gEpA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
On Tue, Jul 04, 2023 at 07:46:23AM +0700, Budi wrote:
> Please one sincerely help, I need huge help
>
> I build kernel but there's few absolute interrupted compilations
> resulting in few .o files are defect, cannot be recognized
>
> In 'make' and 'make modules' this'd be no problem at all as is
> capable of resuming whole the process
> it's solved by deleting those .o files and then redo the build again
> which will complie those particular files only
In that case, you should `make clean` first.
>
> but in 'make modules_install, it won't be
> real case is within Kernel 6.3.9 package
>
> So how to modify the makefile in order to be able to copy/install the
> just built modules in pause-resume fashion so after few particular .o
> files of modules deleted and rebuilt with pause-resume, then the
> modules copy/install is performed on those only, not the entire
> modules
IMO, again `make clean` first then rebuild the whole world (just `make`).
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-07-04 4:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 0:46 Anyone please do big favor, help Budi
2023-07-04 4:01 ` Bagas Sanjaya [this message]
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=ZKOZtP72vmF8d6yi@debian.me \
--to=bagasdotme@gmail.com \
--cc=budikusasi@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.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