Lines Matching refs:make
46 complexity, so one only has to type "make" to build the module. This is
59 An alternative is to use the "make" target "modules_prepare." This will
60 make sure the kernel contains the information required. The target
66 executed to make module versioning work.
72 $ make -C <path_to_kernel_src> M=$PWD
79 $ make -C /lib/modules/`uname -r`/build M=$PWD
84 $ make -C /lib/modules/`uname -r`/build M=$PWD modules_install
90 make -C $KDIR M=$PWD
94 "make" will actually change to the specified directory
105 When building an external module, only a subset of the "make"
108 make -C $KDIR M=$PWD [target]
114 precondition that a successful "make" has been executed for the
140 make -C $KDIR M=$PWD bar.lst
141 make -C $KDIR M=$PWD baz.o
142 make -C $KDIR M=$PWD foo.ko
143 make -C $KDIR M=$PWD /
178 supports building the module using "make" with no arguments.
206 assignments, whereas "make" will see everything except these
208 the first pass is by the "make" instance run on the command
210 initiated by the parameterized "make" in the default target.
266 makefiles, to be used when the "make" and kbuild parts are
405 $ make INSTALL_MOD_PATH=/frodo modules_install
410 calling "make." This has effect when installing both in-tree
421 $ make INSTALL_MOD_DIR=gandalf -C $KDIR \
496 $ make -C $KDIR M=$PWD
513 Use "make" variable KBUILD_EXTRA_SYMBOLS