Re: exported vs command line variables

On Fri, 2016-09-23 at 13:24 +, Edward Welbourne wrote: >> This does seem like an unsound choice, for the reasons David gave, Paul Smith replied: > Perhaps but as discussed, it's been that way in GNU make (and other > versions of make) forever and is required by the POSIX standard. So > we'll j

[bug #49183] Macros set in MAKEFLAGS should not be added to the environment

Follow-up Comment #3, bug #49183 (project make): The current POSIX standard is available online for free and has been for many years now: http://www.opengroup.org/onlinepubs/9699919799/ The change seems pretty innocuous to me. The number of people who set the MAKEFLAGS variable in their local en

[bug #49183] Macros set in MAKEFLAGS should not be added to the environment

Follow-up Comment #2, bug #49183 (project make): But, if a comment is added to the documentation, it would be nice to advise the "unexport" hack from the mailing list. ___ Reply to this item at: __

[bug #49183] Macros set in MAKEFLAGS should not be added to the environment

Follow-up Comment #1, bug #49183 (project make): POSIX or not...that should not add further confusion, by altering a long-establish behaviour of GNU make. BUG? Not really. But if POSIX will to implement their own MAKE, maybe they can follow their own rules, but meanwhile, they still charge an en