litmus-rt.git/scripts/Kbuild.include, branch v2.6.26-rc2

kbuild: fix make V=1

2008-02-11T16:43:54+00:00

When make -s support were added to filechk to
combination created with make V=1 were not
covered.
Fix it by explicitly cover this case too.

Signed-off-by: Sam Ravnborg 
Cc: Mike Frysinger

kbuild: silence CHK/UPD messages according to $(quiet)

2008-02-09T09:43:58+00:00

Signed-off-by: Mike Frysinger 
Signed-off-by: Sam Ravnborg

kbuild: introduce cc-cross-prefix

2007-10-19T19:46:01+00:00

cc-cross-prefix is useful for the architecture that like
to provide a default CROSS_COMPILE value,
but may have several to select between.

Sample usage:

ifneq ($(SUBARCH),$(ARCH))
        ifeq ($(CROSS_COMPILE),)
               CROSS_COMPILE := $(call cc-cross-prefix, m68k-linux-gnu- m68k-linux-)
        endif
endif

Actual usage by the different archs will taken care of later.

Signed-off-by: Sam Ravnborg

kbuild: enable 'make AFLAGS=...' to add additional options to AS

2007-10-15T19:59:31+00:00

The variable AFLAGS is a wellknown variable and the usage by
kbuild may result in unexpected behaviour.
On top of that several people over time has asked for a way to
pass in additional flags to gcc.

This patch replace use of AFLAGS with KBUILD_AFLAGS all over
the tree.

Patch was tested on following architectures:
alpha, arm, i386, x86_64, mips, sparc, sparc64, ia64, m68k, s390

Signed-off-by: Sam Ravnborg

kbuild: enable 'make CFLAGS=...' to add additional options to CC

2007-10-14T20:21:35+00:00

The variable CFLAGS is a wellknown variable and the usage by
kbuild may result in unexpected behaviour.
On top of that several people over time has asked for a way to
pass in additional flags to gcc.

This patch replace use of CFLAGS with KBUILD_CFLAGS all over the
tree and enabling one to use:
make CFLAGS=...
to specify additional gcc commandline options.

One usecase is when trying to find gcc bugs but other
use cases has been requested too.

Patch was tested on following architectures:
alpha, arm, i386, x86_64, mips, sparc, sparc64, ia64, m68k

Test was simple to do a defconfig build, apply the patch and check
that nothing got rebuild.

Signed-off-by: Sam Ravnborg

kbuild: New 'cc-fullversion' macro

2007-07-16T19:15:47+00:00

Prints a six-digit string including the GCC patchlevel.  Also fix
the 'usage' comment for cc-version.

Signed-off-by: Segher Boessenkool 
Signed-off-by: Sam Ravnborg

[PATCH] kbuild: more Makefile cleanups

2007-02-09T18:12:20+00:00

This adds the remaining changes which should have been part of the
review process.

 - the define command is inappropriate (it's primarily for rule
   definitions)
 - execute commands in the current dir as all other commands
 - .*.tmp (but not .*.null) files are also removed up by "make clean"
 - printf has other side effects, just use "echo -e"
 - proper quoting
 - proper indentation

Signed-off-by: Roman Zippel 
Signed-off-by: Linus Torvalds

kbuild: fix space for good (take 103)

2007-02-08T16:16:44+00:00

Michal Ostrowski points out what the real problem was: the spaces at the
start of the definition of the 'checker-shell' make function.

Cc: Michal Ostrowski 
Acked-by: David Miller 
Acked-by: Geert Uytterhoeven 
Acked-by: Oleg Verych 
Signed-off-by: Linus Torvalds

kbuild: make $(checker-shell ) strip spaces around the result

2007-02-08T04:24:25+00:00

It looks like GNU make version 3.80 (but apparently not 3.81) adds
leading whitespace to the result of the checker-shell execution.  This
strips them off explicitly.

Also, don't bother symlinking the output file to /dev/null.  It's likely
as expensive as just writing the temp-file, and we need to remove it
anyway afterwards.

Signed-off-by: Linus Torvalds

[PATCH] kbuild, Kbuild.include: avoid using spaces in call arguments

2007-02-07T23:32:26+00:00

Do not use whitespace in arguments of functions in makefiles, as they
propagate further without notice.  Thus we get

  + echo ' y'

  instead of

  + echo y

Fix misleading comments.

Signed-off-by: Oleg Verych 
Signed-off-by: Linus Torvalds