Messages in this thread Patch in this message | | | Subject | [patch 1/1] doc: describe Kbuild pitfall | From | blaisorblade@yahoo ... | Date | Sat, 19 Mar 2005 17:58:35 +0100 |
| |
From: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it> Cc: Sam Ravnborg <sam@ravnborg.org>
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> ---
linux-2.6.11-paolo/Documentation/kbuild/makefiles.txt | 6 ++++++ 1 files changed, 6 insertions(+)
diff -puN Documentation/kbuild/makefiles.txt~doc-add-pitfall Documentation/kbuild/makefiles.txt --- linux-2.6.11/Documentation/kbuild/makefiles.txt~doc-add-pitfall 2005-03-19 17:52:48.000000000 +0100 +++ linux-2.6.11-paolo/Documentation/kbuild/makefiles.txt 2005-03-19 17:53:57.000000000 +0100 @@ -872,7 +872,13 @@ When kbuild executes the following steps 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 pitfall that bit me once is that whitespace is sometimes + significant; for instance, the below will fail (note the extra space + after the comma): + target: source(s) FORCE + $(call if_changed, ld/objcopy/gzip) ld Link target. Often LDFLAGS_$@ is used to set specific options to ld. _ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |