X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Message-ID: <470E52F8.40706@iki.fi>
Date: Thu, 11 Oct 2007 19:44:40 +0300
From: Andris Pavenis <andris DOT pavenis AT iki DOT fi>
User-Agent: Thunderbird 2.0.0.5 (X11/20070727)
MIME-Version: 1.0
To: Gordon DOT Schumacher AT seagate DOT com
CC: djgpp AT delorie DOT com
Subject: Re: bash-2.0.5b DJGPP port problems
References: <OF0E2AC488 DOT EE9F1280-ON87257371 DOT 0054F6B6-87257371 DOT 005559AE AT seagate DOT com>
In-Reply-To: <OF0E2AC488.EE9F1280-ON87257371.0054F6B6-87257371.005559AE@seagate.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X--MailScanner-Information: Please contact the ISP for more information
X--MailScanner: Found to be clean
X--MailScanner-From: andris DOT pavenis AT iki DOT fi
X-Spam-Status: No
Reply-To: djgpp AT delorie DOT com

Gordon DOT Schumacher AT seagate DOT com wrote:
> Andris Pavenis <andris DOT pavenis AT iki DOT fi> wrote on Thu, 11 Oct 2007 00:09:48
> +0300:
> 
> # There seems to still be serious problems with DJGPP port of bash-2.0.5b
> # from DJGPP beta: on my new computer it fails when trying to configure
> # gcc-4.2.2 for building for DJGPP. Unfortunately the failure is of the
> # worst possible type - it simply jumps out to DOS prompt without any
> # error message when running config.status (invoked from configure which
> # is invoked from djconfig.sh). If the config.status is run directly there
> # is no failure. Enabling tracing (command line option -x added when
> # invoking config.status) shows that last printed command is 'expr 1 + 1'.
> # It is however possible that that the real problem is earlier.
> 
> I am guessing (but only guessing) that it is related to this:
> http://www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp/2006/08/08/16:37:27

Maybe. I don't know. I did not however got SIGSEGV. bash silently quits 
to command prompt.

> I also took a shot at porting bash 3.x to DJGPP a while back but
> wasn't very successful.  That codebase is simply doing too many
> operations that I don't quite understand the what/why for (mostly
> related to state saves and jumps).
> 

Long time ago I also tried to port bash-3.0.0 based on
modifications against original sources from bash-2.0.5b.
It worked in simple tests, but for real work it was still
practically unusable.

Andris