Re: escaped newline in macro expansion in command line

(woops, sorry for replying off-list first; mutt doesn’t like me) Quoth Paul Smith: In your example the backslash is part of a variable expansion: it's INSIDE the variable expansion so it will be handled by make as part of expanding the variable and won't ever be passed to the shell. POSIX.1-20

Re: escaped newline in macro expansion in command line

On Fri, 2021-12-24 at 10:45 +, Humm wrote: > Consider the Makefile: > > .POSIX: > M = word > all: > echo ${M:word=a\ > b} > > I believe, as the escaped newline is in a command line, the expected > behavior is to let the macro expand to i

[bug #58075] getopt.c: compiler warning: add explicit braces to avoid dangling else

Update of bug #58075 (project make): Summary: compiler warning: add explicit braces to avoid dangling else => getopt.c: compiler warning: add explicit braces to avoid dangling else ___ Reply to this item at:

[bug #19113] cannot self-remake makefile starting with './'

Update of bug #19113 (project make): Status:None => Fixed Open/Closed:Open => Closed Fixed Release:None => 3.82 _

escaped newline in macro expansion in command line

(I’m not subscribed to the list.) Consider the Makefile: .POSIX: M = word all: echo ${M:word=a\ b} I believe, as the escaped newline is in a command line, the expected behavior is to let the macro expand to it, and thus to run the command

RE: make -j does not work on RedHat7.7 VM

Hello Smith, Thank you for the comments. I will carefully check our make file configurations. Merry Christmas! Mason -Original Message- From: Paul Smith Sent: Friday, December 24, 2021 12:52 AM To: Zhu, Mason ; bug-make@gnu.org Cc: Gelle, Sreenivasulu ; Zheng, Fred ; Bedalov, Matthew