Skip to content

Commit

Permalink
[PATCH] kbuild: describe Kbuild pitfall
Browse files Browse the repository at this point in the history
Whitespace is significant for make, and I just fought against this... so
please apply this patch.

Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
  • Loading branch information
Paolo 'Blaisorblade' Giarrusso authored and Sam Ravnborg committed Jul 28, 2005
1 parent 61d9cdf commit 4949057
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions Documentation/kbuild/makefiles.txt
Original file line number Diff line number Diff line change
Expand Up @@ -872,7 +872,13 @@ When kbuild executes the following steps are followed (roughly):
Assignments to $(targets) are without $(obj)/ prefix.
if_changed may be used in conjunction with custom commands as
defined in 6.7 "Custom kbuild commands".

Note: It is a typical mistake to forget the FORCE prerequisite.
Another common pitfall is that whitespace is sometimes
significant; for instance, the below will fail (note the extra space
after the comma):
target: source(s) FORCE
#WRONG!# $(call if_changed, ld/objcopy/gzip)

ld
Link target. Often LDFLAGS_$@ is used to set specific options to ld.
Expand Down

0 comments on commit 4949057

Please sign in to comment.