Re: how to (correctly) modify GNU Make so that separate shell is always spawned for each command

[Mark Galeck]

Well, I thought I did describe it.  I apologize if I was not clear.
the output is
Makefile1:1: VAR-Y

(that is, the value is empty) 

      From: Philip Guenther <address@hidden>
 To: Mark Galeck <address@hidden> 
Cc: "address@hidden" <address@hidden>; "address@hidden" <address@hidden>
 Sent: Friday, April 15, 2016 10:48 PM
 Subject: Re: how to (correctly) modify GNU Make so that separate shell is 
always spawned for each command
   
On Fri, Apr 15, 2016 at 10:16 PM, Mark Galeck <address@hidden> wrote:
> I guess you are saying that in fact the Make statement
> export VAR-Y := val
> (attempts to) establish a shell (environment) variable, and is not merely a 
> Make construct. Is that what you are saying?
> But if that is so, then, well, VAR-Y is a valid Make variable (because 
> nothing says otherwise in the Make manual), but is not a valid shell 
> variable, so the above construct might not work for GNU Make, period?
> I thought the above statement must NOT involve  shell at all, precisely 
> because, it is not a valid shell variable.

It would help if you actually showed the EXACT output from running
your hacked make.  As is, it is not clear what exactly you're trying
to describe as happening.


Philip Guenther