X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: Rugxulo Newsgroups: comp.os.msdos.djgpp Subject: DOSEMU + sh -c "./configure && make" Date: Wed, 21 Dec 2011 15:56:29 -0800 (PST) Organization: http://groups.google.com Lines: 31 Message-ID: References: NNTP-Posting-Host: 65.13.115.246 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: posting.google.com 1324511791 16482 127.0.0.1 (21 Dec 2011 23:56:31 GMT) X-Complaints-To: groups-abuse AT google DOT com NNTP-Posting-Date: Wed, 21 Dec 2011 23:56:31 +0000 (UTC) Complaints-To: groups-abuse AT google DOT com Injection-Info: x19g2000yqf.googlegroups.com; posting-host=65.13.115.246; posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO User-Agent: G2/1.0 X-Google-Web-Client: true X-Google-Header-Order: HNKRAUELSC X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.630.0 Safari/534.16,gzip(gfe) Bytes: 2548 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id pBM0F1TZ004687 Reply-To: djgpp AT delorie DOT com Hi, On Dec 21, 4:46 pm, Rugxulo wrote: > > Mainly, I was using this as an example of ./configure hanging (under > DOSEMU, unlike WinXP) at the config.status part (as mentioned > previously re: BRexx). It seems to be a problem with NUL handling (as > mentioned previously re: GNU Emacs). Perhaps I should report it to > Bart Oldeman (DOSEMU dude). For now, though, if anybody cares (doubt > it), maybe you can use this workaround (GNU Autoconf 2.65). I've gone ahead and emailed Bart just for completeness, but a quick search of the DOSEMU bugtracker found something (unrelated) that said this: "[DOSEMU-1.3.3] Failure of DJGPP port of GNU Sed - ID: 1429741" (hi, Andris!) https://sourceforge.net/tracker/index.php?func=detail&aid=1429741&group_id=49784&atid=457447 (2007-5-20, bartoldeman responded): "It is indeed a problem in the FreeDOS kernel. What happens is that SED tries to read from the NUL device in raw mode; that only works correctly in cooked mode. It is fixed in the FreeDOS kernel CVS now." So yeah, upgrading the /usr/lib/dosemu/drive_z/kernel.sys file to latest 2040 version apparently "seems" to have fixed it to work without needing a patch to configure. Just FYI in case anyone else cares (doubt it).