| delorie.com/archives/browse.cgi | search |
| From: | "Mark E." <snowball3 AT bigfoot DOT com> |
| To: | djgpp-workers AT delorie DOT com |
| Date: | Thu, 5 Jul 2001 15:16:52 -0400 |
| MIME-Version: | 1.0 |
| Subject: | Re: Bash... again. |
| Message-ID: | <3B4484E4.5933.1900C@localhost> |
| In-reply-to: | <20010704215038.A204@lauras.lt> |
| X-mailer: | Pegasus Mail for Win32 (v3.12c) |
| Reply-To: | djgpp-workers AT delorie DOT com |
| Errors-To: | nobody AT delorie DOT com |
| X-Mailing-List: | djgpp-workers AT delorie DOT com |
| X-Unsubscribes-To: | listserv AT delorie DOT com |
>
> I'm almost sorry to make alarms at this frequency, but
> I think I've another bash 2.05 bug.
Don't be. There are bound to be problems when there have been a lot of
changes.
Configure scripts by
> autoconf 2.13 give strange results (i.e. make sets
> ${MAKE}...no). I've tracked it to SHELL setting in configure.
I don't like reporting this, but I can't reproduce the problem. Running
./configure works fine even after commenting out the definitions of SHELL and
CONFIG_SHELL in my config.site. Is there a specific package or configure.in
that will show the problem?
MArk
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |