On Sat, Jan 17, 2015 at 12:52 PM, SF Markus Elfring <elfr...@users.sourceforge.net> wrote: >> Of course, if you had actually quoted the relevant lines from your >> Makefile, we could be more precise. > > Thanks for your interest. > > Do you get further ideas from an excerpt of my build script > "parallel-inc.make"? > > Lines 241 - 256: > $(EXIT_CODES_FUNCTIONS_THAT_CHECK_THEIR_SINGLE_PARAMETER_IN_HEADERS) \ > $(RESULT_SQL_DATABASE_NOTIFICATION3) \ > $(RUN_FUNCTIONS_THAT_CHECK_THEIR_SINGLE_PARAMETER_IN_HEADERS): \ > initialise_database \ > $(BUILD_FUNCTIONS_THAT_CHECK_THEIR_SINGLE_PARAMETER_IN_HEADERS) \ > $(HEADER_SEARCH_PARTS) > $(if > $(LET_RUN_FIND_FUNCTIONS_THAT_CHECK_THEIR_SINGLE_PARAMETER_IN_HEADERS_PARALLEL),\ > $(eval > LET_RUN_FIND_FUNCTIONS_THAT_CHECK_THEIR_SINGLE_PARAMETER_IN_HEADERS_PARALLEL::=)$(eval > $(call HANDLE_BACKGROUND_TASK,\ > $(RESULT_SQL_DATABASE_NOTIFICATION3),\ > $(RUN_FUNCTIONS_THAT_CHECK_THEIR_SINGLE_PARAMETER_IN_HEADERS),\ > $(BUILD_FUNCTIONS_THAT_CHECK_THEIR_SINGLE_PARAMETER_IN_HEADERS),\ > $(EXIT_CODES_FUNCTIONS_THAT_CHECK_THEIR_SINGLE_PARAMETER_IN_HEADERS)))) > > find_functions_that_check_their_single_parameter_in_headers_with_parallel_groups: > \ > $(RESULT_SQL_DATABASE_NOTIFICATION3) > @$(ECHO) 'Header files were analysed.'
<wipes tears from eyes> So that $(eval $(call GIBBERISH)) is wrong. Exactly *how* it's wrong depends on what the $(call) is supposed to return. Currently you're evaling something that doesn't look like a *STANDALONE* chunk of Makefile, which results in the error *in the eval*. Paul, I still think $(eval) should have been named $(stick-arm-in-woodchipper), to make it less seductive to people trying to layer imperative programming on the declarative nature of make. Philip Guenther _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
