Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
make dep is used after make xconfig when re-compiling the kernel not sure if this is the best way to compile kernel but I did
make xconfig
make dep
make modules
make modules_install
make bzImage
make install
lilo
not sure all these step have to be done. I'm using makedrake 9.2rc2 and it seems like when you do make install somethings have already been done. well I guess it's alot better than them not getting done at all.
It depends on what program you're trying to compile and install. You don't always need to (or have the option to) run "make clean" or "make check". Most use "make" to build everything, and "make install" to install everything; some also have a "make uninstall" to remove the installation. There aren't any set limitations on the different kind of make rules you can have; it all depends on what the software author has made available in the Makefile. Read 'man make' for more information on how make works.
"make dep" is a rule that some software authors use for building dependencies that are needed before running "make". But again, a lot of packages won't have, and don't need, "make dep". It's always a good idea to read the instructions for anything you're compiling, to find out what's appropriate and necessary for that software.
Originally posted by wapcaplet It depends on what program you're trying to compile and install. You don't always need to (or have the option to) run "make clean" or "make check". Most use "make" to build everything, and "make install" to install everything; some also have a "make uninstall" to remove the installation. There aren't any set limitations on the different kind of make rules you can have; it all depends on what the software author has made available in the Makefile. Read 'man make' for more information on how make works.
"make dep" is a rule that some software authors use for building dependencies that are needed before running "make". But again, a lot of packages won't have, and don't need, "make dep". It's always a good idea to read the instructions for anything you're compiling, to find out what's appropriate and necessary for that software.
Yes, 'make dep' will probably be run before 'make'. But again, be sure to look at the README for whatever you're compiling, since each program is different.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.