www.delorie.com/archives/browse.cgi | search |
Date: | Sun, 23 May 1999 13:38:19 +0300 (IDT) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
X-Sender: | eliz AT is |
To: | Martin Str|mberg <ams AT ludd DOT luth DOT se> |
cc: | DJGPP-WORKERS <djgpp-workers AT delorie DOT com> |
Subject: | Re: Bash 2.03 final beta available |
In-Reply-To: | <199905230955.LAA12331@father.ludd.luth.se> |
Message-ID: | <Pine.SUN.3.91.990523133622.29194C-100000@is> |
MIME-Version: | 1.0 |
Reply-To: | djgpp-workers AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Sun, 23 May 1999, Martin Str|mberg wrote: > > They should go into configure.in. > > Does configure use configure.in to regenerate itself? Or do I need to > run something else (like autoconf or whatever). When you run Autoconf, it uses configure.in to generate configure. > > TMPDIR=${TMPDIR='/tmp'} > > I'm not an expert on sh syntax, but are you sure that's correct > (typo)? Isn't it "TMPDIR=${TMPDIR[ Some other character. ]'/tmp'}"? There are several characters that can be used in this context, I think = is the most appropriate to handle the case that $TMPDIR is already defined.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |