[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: exported vs command line variables
From: |
Philip Guenther |
Subject: |
Re: exported vs command line variables |
Date: |
Fri, 23 Sep 2016 16:34:38 -0700 |
On Fri, Sep 23, 2016 at 4:09 PM, David Boyce <address@hidden> 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 are
> not already in its environment."
>
> And building on Eddy Welbourne's example:
>
> % cat Makefile
> WURGLE = 11
> MAKEFLAGS = WURGLE=$(WURGLE)
You need to read all the applicable bits in the standard before
calling behavior incorrect. In particular, the Macros section has
this line earlier in it:
The result of setting MAKEFLAGS in the Makefile is unspecified.
So if you want POSIX-like behavior, don't do that; if you do that,
you're at the whims of GNU make's choices.
Philip Guenther
- exported vs command line variables, Pietro, 2016/09/20
- Re: exported vs command line variables, Paul Smith, 2016/09/20
- Re: exported vs command line variables, Pietro, 2016/09/21
- Re: exported vs command line variables, David Boyce, 2016/09/23
- Re: exported vs command line variables, Paul Smith, 2016/09/23
- Re: exported vs command line variables, Philip Guenther, 2016/09/23
- Re: exported vs command line variables, David Boyce, 2016/09/23
- Re: exported vs command line variables,
Philip Guenther <=
- Re: exported vs command line variables, Paul Smith, 2016/09/24
- Re: exported vs command line variables, David Boyce, 2016/09/25
- Re: exported vs command line variables, Paul Smith, 2016/09/25
- Re: exported vs command line variables, Edward Welbourne, 2016/09/26
- Re: exported vs command line variables, Edward Welbourne, 2016/09/23