[bug #59154] Multiline environment variables handled poorly

[Kyle Rose]

Follow-up Comment #8, bug #59154 (project make):

[comment #7 comment #7:]
> If the string isn't quoted, the first newline would naturally signal a new
command to the shell, wouldn't it?
> 
> Got an example of a real-world Makefile that would break?

Nope. But that doesn't mean there isn't one.

There are already existing ways to do what you want. I, for instance, use
structures like:

echo -e $(call quote-sh,$(subst $(NL),$(backslash)n,$(mystring)))

to do this (in part because "$(mystring)" doesn't work as expected when
$(mystring) contains a double quote).

Finally, does make even parse double quotes in the recipes currently?
Doubtful, and I'm not sure I'd want to add that functionality.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59154>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/