|
From: | Brian Vandenberg |
Subject: | [bug #47960] Adding variable assignment and new rule in else, break execution. |
Date: | Thu, 19 May 2016 13:50:21 +0000 (UTC) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; Win64; x64; Trident/7.0; rv:11.0) like Gecko |
Follow-up Comment #1, bug #47960 (project make): If anything I think it would be best to avoid allowing this sort of thing. I'm having trouble reproducing a situation I ran into a year or so ago, but it looked something like this: # As you might guess targets.mk has targets in it include rules/paths.mk rules/tools.mk rules/flags.mk rules/targets.mk include /a/list/of/makefile/stubs/for/various/projects ... then in one of the makefile stubs: # some assignments a=a b=b #... z=z # vpath stuff #... ifeq "something" "${something else}" # note the tab; my editor decided to be "helpful" some valid make statement #^^^^^^^ # This caused it to associate the line with a recipe that came from targets.mk else # in here there's spaces some other valid make statement endif _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?47960> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |