linux-toradex.git/scripts/Kbuild.include, branch v2.6.22-rc7

[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

[PATCH] kbuild: improve option checking, Kbuild.include cleanup

2007-02-06T22:30:49+00:00

 GNU binutils, root users, tmpfiles, external modules ro builds must
 be fixed to do the right thing now.

Cc: Roman Zippel 
Cc: Sam Ravnborg 
Cc: Horst Schirmeier 
Cc: Jan Beulich 
Cc: Daniel Drake 
Cc: Andi Kleen 
Cc: Randy Dunlap 
Signed-off-by: Oleg Verych 
Signed-off-by: Linus Torvalds

[PATCH] kbuild: don't put temp files in source

2006-12-10T17:55:39+00:00

The as-instr/ld-option need to create temporary files, but create them in the
output directory, when compiling external modules.  Reformat them a bit and
use $(CC) instead of $(AS) as the former is used by kbuild to assemble files.

Signed-off-by: Roman Zippel 
Cc: Andi Kleen 
Cc: Jan Beulich 
Cc: Sam Ravnborg 
Cc: 
Cc: Horst Schirmeier 
Cc: Daniel Drake 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] i386/x86-64: Work around gcc bug with noreturn functions in unwinder

2006-09-26T08:52:41+00:00

Current gcc generates calls not jumps to noreturn functions. When that happens the
return address can point to the next function, which confuses the unwinder.

This patch works around it by marking asynchronous exception
frames in contrast normal call frames in the unwind information.  Then teach
the unwinder to decode this.

For normal call frames the unwinder now subtracts one from the address which avoids
this problem.  The standard libgcc unwinder uses the same trick.

It doesn't include adjustment of the printed address (i.e. for the original
example, it'd still be kernel_math_error+0 that gets displayed, but the
unwinder wouldn't get confused anymore.

This only works with binutils 2.6.17+ and some versions of H.J.Lu's 2.6.16
unfortunately because earlier binutils don't support .cfi_signal_frame

[AK: added automatic detection of the new binutils and wrote description]

Signed-off-by: Jan Beulich 
Signed-off-by: Andi Kleen

[PATCH] x86: Detect CFI support in the assembler at runtime

2006-09-26T08:52:30+00:00

... instead of using a CONFIG option. The config option still controls
if the resulting executable actually has unwind information.

This is useful to prevent compilation errors when users select
CONFIG_STACK_UNWIND on old binutils and also allows to use
CFI in the future for non kernel debugging applications.

Cc: jbeulich@novell.com
Cc: sam@ravnborg.org

Signed-off-by: Andi Kleen

kbuild: make V=2 tell why a target is rebuild

2006-09-25T07:01:49+00:00

tell why a a target got build
   enabled by make V=2
      Output (listed in the order they are checked):
         (1) - due to target is PHONY
         (2) - due to target missing
         (3) - due to: file1.h file2.h
         (4) - due to command line change
         (5) - due to missing .cmd file
         (6) - due to target not in $(targets)
(1) We always build PHONY targets
(2) No target, so we better build it
(3) Prerequisite is newer than target
(4) The command line stored in the file named dir/.target.cmd
    differed from actual command line. This happens when compiler
    options changes
(5) No dir/.target.cmd file (used to store command line)
(6) No dir/.target.cmd file and target not listed in $(targets)
    This is a good hint that there is a bug in the kbuild file

This patch is inspired by a patch from: Milton Miller 

Cc: Milton Miller 
Signed-off-by: Sam Ravnborg

kbuild: consistently decide when to rebuild a target

2006-09-25T07:00:00+00:00

Consistently decide when to rebuild a target across all of
if_changed, if_changed_dep, if_changed_rule.
PHONY targets are now treated alike (ignored) for all targets

While add it make Kbuild.include almost readable by factoring out a few
bits to some common variables and reuse this in Makefile.build.

Signed-off-by: Sam Ravnborg