[Top][All Lists]

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

[bug #19626] Unexpected environment variable modification in command

From: Paul D. Smith
Subject: [bug #19626] Unexpected environment variable modification in command
Date: Wed, 18 Apr 2007 12:47:29 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20060601 Firefox/ (Ubuntu-edgy)

Update of bug #19626 (project make):

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


Follow-up Comment #1:

This is the way make is documented to work; from the GNU make manual, section
"Variables from the Environment":

   When `make' runs a command script, variables defined in the makefile
are placed into the environment of that command.  This allows you to
pass values to sub-`make' invocations (*note Recursive Use of `make':
Recursion.).  By default, only variables that came from the environment
or the command line are passed to recursive invocations.  You can use
the `export' directive to pass other variables.  *Note Communicating
Variables to a Sub-`make': Variables/Recursion, for full details.

With the single exception of the SHELL variable, all environment variables
are imported as make variables when make starts, and automatically marked as
exported so that when make runs a command their current values will be
exported into the environment of the command.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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