[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #59154] Multiline environment variables handled poorly

From: Kyle Rose
Subject: [bug #59154] Multiline environment variables handled poorly
Date: Tue, 22 Sep 2020 12:02:22 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

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:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]