On Thu, Apr 3, 2025 at 3:35 PM Cook, Malcolm wrote:
> I was surprised when setting SHELL (e.g. to `duckdb`) to find that a simply
> expanded variable that expands to $(shell some sh command) wound up passing
> 'my sh command' to duckdb rather than /bin/sh since It was expanded as part
> of a re
> -Original Message-
> From: Cook, Malcolm
> Sent: Wednesday, April 9, 2025 8:14 AM
> To: Dmitry Goncharov
> Cc: help-make@gnu.org
> Subject: RE: using $(shell some sh command) when .SHELL has been
> (temporarily) set to non
>
> Sure, thanks for taking an inte
itry Goncharov
> Sent: Wednesday, April 9, 2025 6:45 AM
> To: Cook, Malcolm
> Cc: help-make@gnu.org
> Subject: Re: using $(shell some sh command) when .SHELL has been
> (temporarily) set to non
>
> On Thu, Apr 3, 2025 at 3:35 PM Cook, Malcolm wrote:
> >
> > I ex
On Thu, Apr 3, 2025 at 3:35 PM Cook, Malcolm wrote:
>
> I expect GNU make is working as expected, but I could use confirmation
>
> I was surprised when setting SHELL (e.g. to `duckdb`) to find that a simply
> expanded variable that expands to $(shell some sh command) wound up passing
> 'my
