X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Recipient:	djgpp-workers AT delorie DOT com
Message-ID:	<52ADBDCB.2020203@gmx.de>
Date:	Sun, 15 Dec 2013 15:33:47 +0100
From:	Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de>
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: Attempts to build GCC under DOSEMU
References:	<52AD9B08 DOT 1040501 AT iki DOT fi>
In-Reply-To:	<52AD9B08.1040501@iki.fi>
X-Provags-ID:	V03:K0:IkHUfze/Cpb7oEr5NeDQIBHPClKi4LW68l2FhV5pP+lw5ygZt6C
	Cyj1SI7inC/11qLm9UPM2xOch3yEPM7kkHpj1BcKz4VDo0cBbOxCRv6hynoMYGgKH77AZNh
	ptQrpGORYyBx+pZyby4vA7E/NnXn1YmMUTEVLIcqeHG8mb6vk44FJKlxzCRyCgxTalI7zBo
	SlDX2pLSTShfzfOyIobaw==
Reply-To:	djgpp-workers AT delorie DOT com

Am 15.12.2013 13:05, schrieb Andris Pavenis:
> I'm trying to build gcc-4.8.2 under DOSEMU (in Fedora 19 x86_64)
>
> 1) The first problem was that top level configure script failed
> when trying to run config.status. Narrowed down the problem to
> the starting sed:
>
> simplified example:
>
> sed -e 's:foo:bar:g' </dev/null
>
> worked OK (empty output) in DOS session under Windows Vista,
> but outputed garbage under Dosemu. Rebuilding sed using
> current DJGPP CVS version did not help. However upgrading
> FreeDOS image to FreeDOS-1.1 did, so after that top level
> configure finished OK
>
> 2) The second problem was creating config.status in gcc
> subdirectory. In this case
>
> awk 'BEGIN {getline < "/dev/null"}'
>
> gets stuck (with FreeDOS-1.1). One can try one of the following:
> echo "" | awk 'BEGIN  {getline < "/dev/null"}'
> awk 'BEGIN  {getline < "/dev/null"}' </dev/null
>
> Perhaps the next step would be to rebuild awk and try
> to debug the problem.
>
> I do not know whether one have similar problems when
> using FreeDOS 1.1 directly or in virtual machine.
>
> Andris
>

I have tried this (gawk 'BEGIN {getline < "/dev/null"}' ) on vmware using winxp and msdos 6.22.
It works flawlessly.  But with freedos 1.1 it fails.  Will put the issue on my todo list but it will take
some time.

Regards,
Juan M. Guerrero

- Raw text -