On Fri, Sep 23, 2016 at 4:09 PM, David Boyce wrote:
> In that case there does seem to be at least one bug here. In reference to
> the sentence:
>
> "Macros defined by the MAKEFLAGS environment variable and macros defined in
> the makefile(s) shall not be added to the environment of make if they ar
In that case there does seem to be at least one bug here. In reference to
the sentence:
"Macros defined by the MAKEFLAGS environment variable and macros defined in
the makefile(s) shall not be added to the environment of make if they are
not already in its environment."
And building on Eddy Welbo
On Fri, Sep 23, 2016 at 11:23 AM, Paul Smith wrote:
> On Fri, 2016-09-23 at 05:52 -0700, David Boyce wrote:
>> I still think that's a good plan, except that now I find out it ends
>> up exporting anyway. I'm sure it's too late to change now but is
>> there a reason for this (unfortunate IMHO) beha
David Boyce observed:
> I was unpleasantly surprised to learn while following this discussion
> that "Except by explicit request, make exports a variable only if it
> is either defined in the environment initially _or set on the command
> line_".
... and I was surprised to find (by experiment with
On Fri, 2016-09-23 at 05:52 -0700, David Boyce wrote:
> I still think that's a good plan, except that now I find out it ends
> up exporting anyway. I'm sure it's too late to change now but is
> there a reason for this (unfortunate IMHO) behavior?
I can't tell you: this behavior has existed since t
Changing the subject a bit, I was unpleasantly surprised to learn while
following this discussion that "Except by explicit request, make exports a
variable only if it is either defined in the environment initially _or set
on the command line_". For years I've noticed a tendency for users to mark
va
