Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
From: pg@sweng.stortek.com
Message-id: <200004102356.RAA02369@sanitas>
Subject: Re: Passing ENV vars to sub-configures
To: new-httpd@apache.org
Date: Mon, 10 Apr 2000 17:56:47 -0600 (MDT)
In-Reply-To: <200004102341.TAA24929@devsys.jaguNET.com> from "Jim Jagielski"
 at Apr 10, 2000 07:41:16 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

In a recent note, Jim Jagielski said:

> Date: Mon, 10 Apr 2000 19:41:16 -0400 (EDT)
> 
> pg@sweng.stortek.com wrote:
> > 
> > In a recent note, Jim Jagielski said:
> > 
> > > Date: Mon, 10 Apr 2000 17:43:01 -0400 (EDT)
> > > 
> > > > > One problem with the current configure setup is that env. variables
> > > > > used at the top level aren't passed to the lower level configures.
> > > > > 
> > > > >     CC="c89" CFLAGS="-O5" LIBS="-lflurbl" ./configure
> > > 
> > > They are placed in the environment but not _exported_.
> > > 
> >     pg@sanitas:334$ GLOBAL=Global /bin/ksh
> > 
> You're looking at it wrong.
> 
> Do this:
> 
>     $ sh
>     $ FOOBAR='test'
>     $ set
>     $ sh
>     $ set
> 
> you will note that FOOBAR is not around in the 2nd shell. Otherwise,
> what is the need for export???
> 
We're looking at it differently.  Assignments that appear preceding a
command on the same line, as in your "./configure" example, and in
my "/bin/ksh" example are exported.  Assignments that appear on a
line solo, as in your "sh" example are not exported, as you correctly
observe.  In your first example, I'd expect the three variables
to be exported within the environment of configure.

-- gil
-- 
StorageTek
INFORMATION made POWERFUL