From: mudongliangabcd@gmail.com (mudongliang)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Without "make modules" command, we can also execute "make modules_install" command?
Date: Thu, 08 Oct 2015 22:32:59 +0800 [thread overview]
Message-ID: <56167E9B.2060904@gmail.com> (raw)
In-Reply-To: <CA+MhoaNmi-xDGVzTg-Yj0xOPdmq7S5zoCFDr2sXiWjbWYscitQ@mail.gmail.com>
On 10/08/2015 03:02 PM, Nan Xiao wrote:
> Hi all,
>
> From KernelBuild <http://kernelnewbies.org/KernelBuild> post, I don't
> see "make modules" command. This article only executes "make"
> command before "sudo make modules_install install".
>
> So I am a little confused, is "make modules" optional in building
> kernel? No "make modules" command,
> we can also execute "make modules_install" command?
>
From "make help", you can see the following output:
...
all - Build all targets marked with [*]
* vmlinux - Build the bare kernel
* modules - Build all modules
modules_install - Install all modules to INSTALL_MOD_PATH (default: /)
...
* bzImage - Compressed kernel image (arch/x86/boot/bzImage)
...
install - Install kernel using
(your) ~/bin/installkernel or
(distribution) /sbin/installkernel or
install to $(INSTALL_PATH) and run lilo
- mudongliang
> Thanks very much in advance!
>
> Best Regards
> Nan Xiao
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20151008/c6150891/attachment.html
prev parent reply other threads:[~2015-10-08 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 7:02 Without "make modules" command, we can also execute "make modules_install" command? Nan Xiao
2015-10-08 14:32 ` mudongliang [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=56167E9B.2060904@gmail.com \
--to=mudongliangabcd@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).