www.delorie.com/archives/browse.cgi | search |
Date: | Mon, 24 May 1999 16:19:28 +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: #!/bin/sh and not LFN |
In-Reply-To: | <199905241153.NAA26425@father.ludd.luth.se> |
Message-ID: | <Pine.SUN.3.91.990524161758.7396F-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 Mon, 24 May 1999, Martin Str|mberg wrote: > Yes, it's using "${CONFIG_SHELL-/bin/sh}", and as CONFIG_SHELL is > never set it uses "/bin/sh". > > Is CONFIG_SHELL shell something that should be set (from the > perspectives a normal bash user and a developing bash user)? I usually set it in the batch file that runs configure. If Bash is configured by a DJGPP-specific shell script, then that script should set CONFIG_SHELL.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |