Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit df291fa9 authored by Randy Dunlap's avatar Randy Dunlap Committed by Sam Ravnborg
Browse files

kbuild: fix kbuild.txt typos 



Fix typos in the new kbuild.txt file.

Signed-off-by: default avatarRandy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
parent 2302e873

Documentation/kbuild/kbuild.txt

+15 −14
Original line number Diff line number Diff line
@@ -3,7 +3,7 @@ Environment variables 
KCPPFLAGS

--------------------------------------------------

Additional options to pass when preprocessing. The preprocessing options

will be used in all cases where kbuild do preprocessing including

will be used in all cases where kbuild does preprocessing including

building C files and assembler files.



KAFLAGS
@@ -16,7 +16,7 @@ Additional options to the C compiler. 


KBUILD_VERBOSE

--------------------------------------------------

Set the kbuild verbosity. Can be assinged same values as "V=...".

Set the kbuild verbosity. Can be assigned same values as "V=...".

See make help for the full list.

Setting "V=..." takes precedence over KBUILD_VERBOSE.
@@ -35,14 +35,14 @@ KBUILD_OUTPUT 
--------------------------------------------------

Specify the output directory when building the kernel.

The output directory can also be specificed using "O=...".

Setting "O=..." takes precedence over KBUILD_OUTPUT

Setting "O=..." takes precedence over KBUILD_OUTPUT.



ARCH

--------------------------------------------------

Set ARCH to the architecture to be built.

In most cases the name of the architecture is the same as the

directory name found in the arch/ directory.

But some architectures suach as x86 and sparc has aliases.

But some architectures such as x86 and sparc have aliases.

x86: i386 for 32 bit, x86_64 for 64 bit

sparc: sparc for 32 bit, sparc64 for 64 bit
@@ -63,7 +63,7 @@ CF is often used on the command-line like this: 
INSTALL_PATH

--------------------------------------------------

INSTALL_PATH specifies where to place the updated kernel and system map

images. Default is /boot, but you can set it to other values

images. Default is /boot, but you can set it to other values.





MODLIB
@@ -90,7 +90,7 @@ INSTALL_MOD_STRIP will used as the options to the strip command. 


INSTALL_FW_PATH

--------------------------------------------------

INSTALL_FW_PATH specify where to install the firmware blobs.

INSTALL_FW_PATH specifies where to install the firmware blobs.

The default value is:



    $(INSTALL_MOD_PATH)/lib/firmware
@@ -99,7 +99,7 @@ The value can be overridden in which case the default value is ignored. 


INSTALL_HDR_PATH

--------------------------------------------------

INSTALL_HDR_PATH specify where to install user space headers when

INSTALL_HDR_PATH specifies where to install user space headers when

executing "make headers_*".

The default value is:
@@ -112,22 +112,23 @@ The value can be overridden in which case the default value is ignored. 


KBUILD_MODPOST_WARN

--------------------------------------------------

KBUILD_MODPOST_WARN can be set to avoid error out in case of undefined

symbols in the final module linking stage.

KBUILD_MODPOST_WARN can be set to avoid errors in case of undefined

symbols in the final module linking stage. It changes such errors

into warnings.



KBUILD_MODPOST_FINAL

KBUILD_MODPOST_NOFINAL

--------------------------------------------------

KBUILD_MODPOST_NOFINAL can be set to skip the final link of modules.

This is solely usefull to speed up test compiles.

This is solely useful to speed up test compiles.



KBUILD_EXTRA_SYMBOLS

--------------------------------------------------

For modules use symbols from another modules.

For modules that use symbols from other modules.

See more details in modules.txt.



ALLSOURCE_ARCHS

--------------------------------------------------

For tags/TAGS/cscope targets, you can specify more than one archs

to be included in the databases, separated by blankspace. e.g.

For tags/TAGS/cscope targets, you can specify more than one arch

to be included in the databases, separated by blank space. E.g.:



    $ make ALLSOURCE_ARCHS="x86 mips arm" tags