[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #46585] variables being auto-exported to the environment if it was

From: Paul D. Smith
Subject: [bug #46585] variables being auto-exported to the environment if it was set in the environment
Date: Mon, 26 Dec 2016 16:53:28 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0

Update of bug #46585 (project make):

                  Status:                    None => Not A Bug              
             Open/Closed:                    Open => Closed                 


Follow-up Comment #3:

See also duplicate bug #48360.

I've reviewed the POSIX spec and it does seem to say that GNU make's current
behavior is the expected one; I see this (although in the Rationale section:

_The environment is the same as the environment to make except that MAKEFLAGS
and macros defined on the make command line are added, and except that macros
defined by the MAKEFLAGS environment variable and macros defined in the
makefile(s) may update the value of an existing environment variable (other
than SHELL)._

I don't see any great way to avoid this; many makefiles have been written
expecting this behavior (consider, for example, resetting common environment
variables such as PATH, etc.) so we can't just turn it off completely... and
makefile writers already have a way to avoid exporting variables they don't
want to export (via the unexport command).


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]