X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Message-ID: <470D3F9C.3020800@iki.fi>
Date: Thu, 11 Oct 2007 00:09:48 +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: "DJGPP List (E-mail)" <djgpp AT delorie DOT com>
Subject: bash-2.0.5b DJGPP port problems
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

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.

If the config.status is run manually and Makefile is created, then 
trying to run ./djmake.sh bootstrap ends in the same way (I did not 
study in more details). I should perhaps receck on my old computer, 
where I have not seen similar problems when building GCC for a long 
time. Copied over exact copy of DJGPP directory from old computer (where 
earlier builds were done), but it did not fix the problem.

As one can easily understand the debugging of such problem is very 
difficult.

System information:

CPU: Intel Core 2 Quad (2.4GHz)
Memory: 2 Gb
Windows XP + SP2 + latest updates from M$

On old computer I had: Pentium 4 2.8GHz, initially 1Gb (but had to 
remove 512Mb due to hardware problems), Windows XP + SP2

The problem does not appear if bash-2.0.4 is used instead (I did not 
however finish the build, but at least it does not crash in the same place)

Andris