X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com X-Authenticated: #27081556 X-Provags-ID: V01U2FsdGVkX187qB4TbQM7VANrqxzQ3S99iGKrT1SBrg/AGVmZk0 X9rkMgcwJk7mbG From: Juan Manuel Guerrero To: djgpp AT delorie DOT com Subject: Re: DOSEMU : sh -c "./configure" : hangs when making config.status Date: Sun, 3 Jul 2011 18:03:38 +0200 User-Agent: KMail/1.9.10 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201107031803.38427.juan.guerrero@gmx.de> X-Y-GMX-Trusted: 0 I have tried to configure brexx-2.1.9.tar.gz on WinXP Pro SP3 installed on VMware using stock DJGPP 2.04 toolchain. This means I always use the latest ports of everthing; especially bsh205bbr3. I started the configure script without any options. Sometimes the configuration dies with the following error message: [snip] checking for strstr... yes configure: creating ./config.status malloc: dispose_cmd.c:226: assertion botched free: start and end chunk sizes differ Stopping myself...Abort! Exiting due to signal SIGABRT Raised at eip=00082fbf eax=0012ea6c ebx=00000120 ecx=00130008 edx=00000001 esi=00071ed0 edi=000000e2 ebp=0012eb18 esp=0012ea50 program=C:\DJGPP-2.04\BIN\SH.EXE cs: sel=01a7 base=02990000 limit=0030ffff ds: sel=01af base=02990000 limit=0030ffff es: sel=01af base=02990000 limit=0030ffff fs: sel=017f base=00008ad0 limit=0000ffff gs: sel=01bf base=00000000 limit=0010ffff ss: sel=01af base=02990000 limit=0030ffff App stack: [0012ee00..000aee04] Exceptn stack: [000ae448..000ac508] Call frame traceback EIPs: 0x00082ef4 0x00082fbf 0x0007d650 0x0001a647 0x00071e14 0x00071fe1 0x00010271 0x00010373 0x000106b1 0x00010673 0x000048b0 0x00004192 0x00074dfb F:\BREXX-~1.9> It is very difficult to reproduce because if I start the script a second time the configuration may finish successfully producing and running the config.status script. A comparision of the config.status files produced when the configuration passes successfully and the case when the configuration fails shows that sometimes they are identical and sometimes they are not. Starting the complete config.status alone produces the required Makefiles and headers. I replaced bsh205bbr3 with bsh205bbr2 and I had no longer this fealure. Please note that I tried only ten times to configure the sources using bsh205bbr2 so there is no guarantee that replacing the bashes will really solve the issue. Anyway, compiling the sources out-of-the-box does not work because it requires wcslen that is not provided by djgpp so I think that a closer look to th whole source code may be required. Please note that I will not be able to solve the bash problem. In the end we need a port of the current bash version and this will be a mayor job. Regards, Juan M. Guerrero