user/sven/linux.git/scripts/Makefile.build, branch v2.6.16.5

kbuild: introduce escsq to escapre single quotes

2006-01-06T21:35:59Z

This makes things a little bit more reader friendly and gvim is less confused. Signed-off-by: Sam Ravnborg

kbuild: fix building external modules

2005-07-27T20:11:01Z

kbuild failed to locate Makefile for external modules. This brought to my attention how the variables for directories have different values in different usage scenarios. Different kbuild usage scenarios: make - plain make in same directory where kernel source lives make O= - kbuild is told to store output files in another directory make M= - building an external module make O= M= - building an external module with kernel output seperate from src Value assigned to the different variables: |$(src) |$(obj) |$(srctree) |$(objtree) make |reldir to k src |as src |abs path to k src |abs path to k src make O= |reldir to k src |as src |abs path to k src |abs path to output dir make M= |abs path to src |as src |abs path to k src |abs path to k src make O= M= |abs path to src |as src |abs path to k src |abs path to k output path to kbuild file: make | $(srctree)/$(src), $(src) make O= | $(srctree)/$(src) make M= | $(src) make O= M= | $(src) From the table above it can be seen that the only good way to find the home directory of the kbuild file is to locate the one of the two variants that is an absolute path. If $(src) is an absolute path (starts with /) then use it, otherwise prefix $(src) with $(srctree). Signed-off-by: Sam Ravnborg

kbuild: fix make O=...

2005-07-25T20:26:04Z

kbuild failed to locate Kbuild.include. Teach kbuild how to find Kbuild files when using make O=... Signed-off-by: Sam Ravnborg ---

kbuild: introduce Kbuild.include

2005-07-25T20:10:36Z

Kbuild.include is a placeholder for definitions originally present in both the top-level Makefile and scripts/Makefile.build. There were a slight difference in the filechk definition, so the most videly used version was kept and usr/Makefile was adopted for this syntax. Signed-off-by: Sam Ravnborg ---

kbuild: Fix build as root then user

2005-07-14T20:12:40Z

From: Matthew Wilcox I inadvertently built a tree as root and then rebuilt it as a user. I got a lot of prompts ... mv: overwrite `drivers/char/drm/drm_auth.o', overriding mode 0644? Using mv -f fixes that. Signed-off-by: Matthew Wilcox Signed-off-by: Sam Ravnborg

[PATCH] apply quotation handling to Makefile.build

2005-06-23T16:45:28Z

Adding quotation handling to rule_cc_o_c in scripts/Makefile.build as used elsewhere. Signed-off-by: Jan Beulich Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

kbuild: Use -isystem `gcc --print-file-name=include`

2004-12-29T01:15:39Z

Using "-nostdinc -isystem `gcc --print-file-name=include" let us see full path to compiler specific files when compiling with make V=1 Furthermore it lets us use same definition for sparse (CHECKFLAGS) and the kernel. Tested with gcc 3.3.4 only. Signed-off-by: Sam Ravnborg

Merge mars.ravnborg.org:/home/sam/bk/linux-2.6

2004-11-04T00:40:52Z

into mars.ravnborg.org:/home/sam/bk/to-akpm

kbuild: Prefer Kbuild as name of the kbuild files

2004-11-03T22:40:43Z

The kbuild syntax is unique and does only have very few things in common with usual Makefile syntax. So to avoid confusion make the filename 'Kbuild' be the preferred name as replacement for 'Makefile'. No global renaming planned to take place for now, but new stuff expected to use the new 'Kbuild' filename. Signed-off-by: Sam Ravnborg

Make sparse pick up the gcc internal include directory automatically.

2004-10-31T04:58:51Z

m68k used to do this by hand, but it really ends up being needed for any environment that does cross-builds, so just do it unconditionally. This should mean that you never need to cross-build sparse or have any other hacks for checking a cross-built environment.