Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If you ever cared to read the README plaintext file that comes along the sources, you wouldn't have asked - it's all covered there. I recall there used to be a "make all" target, but nowadays if I'm right it's just "make" (no "all"). Referring to the README file of 2.6.23.1:
Quote:
COMPILING the kernel:
- Make sure you have at least gcc 3.2 available.
For more information, refer to Documentation/Changes.
Please note that you can still run a.out user programs with this kernel.
- Do a "make" to create a compressed kernel image. It is also
possible to do "make install" if you have lilo installed to suit the
kernel makefiles, but you may want to check your particular lilo setup first.
To do the actual install you have to be root, but none of the normal
build should require that. Don't take the name of root in vain.
- If you configured any of the parts of the kernel as `modules', you
will also have to do "make modules_install".
As you see, no "make all" there. But like I said, I think the older kernels had that option (along with the other 'make's). Anyway when compiling something from source you haven't written yourself (maybe even then), always read the documentation first to get a picture of how it should be done. Especially for a kernel, which is more or less crucial to get your system up, there is no sane reason to check out at least the most common of documentation files, README (and/or INSTALL), to see what should be done. It really doesn't take that much time, and because things can change (you don't compile Linux kernel nowadays the way you used to do it with version 1) it's a good idea to have your information up to date.
Read the README and/or INSTALL files always, and any other documentation present.
...and besides that, in a more generic way, you can always run 'make -n all', which will run make but only show what it would do, not actually do things.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.