From: Johannes Berg <johannes.berg@xxxxxxxxx> Catch running make in the backport template directory by checking for the .local-symbols file. If it isn't there then we're in the input/template directory rather than in an output tree, give the user a hint about it instead of keeling over. Signed-off-by: Johannes Berg <johannes.berg@xxxxxxxxx> --- backport/Makefile | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/backport/Makefile b/backport/Makefile index 287b27d..f0c7586 100644 --- a/backport/Makefile +++ b/backport/Makefile @@ -37,6 +37,18 @@ mrproper: @rm -f backport-include/backport/autoconf.h .DEFAULT: + @set -e ; test -f .local-symbols || ( \ + echo "/--------------" ;\ + echo "| You shouldn't run make in the backports tree, but only in" ;\ + echo "| the generated output. This here is only the skeleton code" ;\ + echo "| copied into the output directory. To use the backport system" ;\ + echo "| from scratch, go into the top-level directoroy and run" ;\ + echo "| ./gentree.py /path/to/linux-next/ /tmp/output" ;\ + echo "| and then make menuconfig/... in the output directory. See" ;\ + echo "| ./gentree.py --help" ;\ + echo "| for more options." ;\ + echo "\\--" ;\ + false) @set -e ; test -f $(KERNEL_CONFIG) || ( \ echo "/--------------" ;\ echo "| Your kernel headers are incomplete/not installed." ;\ -- 1.8.0 -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html