delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/01/10/20:02:41

From: elric AT wheel DOT dcn DOT davis DOT ca DOT us (Jeffrey Taylor)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: BASH startup
Date: 10 Jan 1997 17:33:03 GMT
Organization: Davis Community Network - Davis, California, USA
Lines: 17
Message-ID: <5b5ugf$2uf$1@mark.ucdavis.edu>
References: <5b0thq$g5e$1 AT mark DOT ucdavis DOT edu> <5b1076$nb0$1 AT mark DOT ucdavis DOT edu> <32D47DAB DOT 38B1 AT cs DOT com> <01bbfe2a$d10ea4e0$0f02000a AT weiqigao> <32D59D09 DOT 2BF4 AT cs DOT com>
NNTP-Posting-Host: wheel.dcn.davis.ca.us
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

John M. Aldrich (fighteer AT cs DOT com) wrote:
: Weiqi Gao wrote:
: > 
: > Yes.  The current shell gets the variable whether you export or not.
: > Subshells gets the variable only after you export it.  Is that how it works
: > in ksh?
: 
: In ksh, any variables that are not exported only exist in the context of
: the current shell, and are not retained by the parent when that shell
: exits.  So, if you write a script, but don't export your variables, they
: will only exist in the context of that script.
: 

This was my problem, by exporting the variables I needed for make and gcc,
it all wroks.  Thanks to everyone for their help.

Jeff T

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019