Lines Matching refs:make
49 complexity, so one only has to type "make" to build the module. This is
63 An alternative is to use the "make" target "modules_prepare." This will
64 make sure the kernel contains the information required. The target
70 executed to make module versioning work.
77 $ make -C <path_to_kernel_src> M=$PWD
84 $ make -C /lib/modules/`uname -r`/build M=$PWD
89 $ make -C /lib/modules/`uname -r`/build M=$PWD modules_install
96 make -C $KDIR M=$PWD
100 "make" will actually change to the specified directory
112 When building an external module, only a subset of the "make"
115 make -C $KDIR M=$PWD [target]
121 precondition that a successful "make" has been executed for the
149 make -C $KDIR M=$PWD bar.lst
150 make -C $KDIR M=$PWD baz.o
151 make -C $KDIR M=$PWD foo.ko
152 make -C $KDIR M=$PWD ./
189 supports building the module using "make" with no arguments.
218 assignments, whereas "make" will see everything except these
220 the first pass is by the "make" instance run on the command
222 initiated by the parameterized "make" in the default target.
281 makefiles, to be used when the "make" and kbuild parts are
429 $ make INSTALL_MOD_PATH=/frodo modules_install
434 calling "make." This has effect when installing both in-tree
446 $ make INSTALL_MOD_DIR=gandalf -C $KDIR \
527 $ make -C $KDIR M=$PWD
532 Use "make" variable KBUILD_EXTRA_SYMBOLS