[PATCH] kbuild: describe Kbuild pitfall
authorPaolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Thu, 28 Jul 2005 15:56:17 +0000 (17:56 +0200)
committerSam Ravnborg <sam@mars.(none)>
Thu, 28 Jul 2005 20:58:21 +0000 (22:58 +0200)
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>
Documentation/kbuild/makefiles.txt

index 2616a58a5a4b829a3fb951e305cf6af37aee4cfa..9a1586590d827fcb11943247362c527dbe419105 100644 (file)
@@ -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.