[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: exported vs command line variables
From: |
Edward Welbourne |
Subject: |
Re: exported vs command line variables |
Date: |
Fri, 23 Sep 2016 13:24:02 +0000 |
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
<file name="Makefile">
default:
/usr/bin/env
</file> invoked via make WURGLE=8, finding this indeed reported by env)
that this really does mean export *to the environment*, where I had
supposed it was exported only to subordinate make invocations (by virtue
of being part of MAKEFLAGS).
This does seem like an unsound choice, for the reasons David gave,
Eddy.
- Re: exported vs command line variables, (continued)
- 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, 2016/09/23
- 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 <=