To:	djgpp AT delorie DOT com
Subject:	Re: Failed compilation of GCC 2.8.1
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 990511090929 DOT 7567E-100000 AT is> <Pine DOT GSO DOT 3 DOT 95 DOT 990512004606 DOT 16213B-100000 AT holyrood DOT ed DOT ac DOT uk>
From:	Michael Bukin <M DOT A DOT Bukin AT inp DOT nsk DOT su>
Date:	12 May 1999 08:54:32 +0700
In-Reply-To:	Daniel Barker's message of "Wed, 12 May 1999 00:48:04 +0100"
Message-ID:	<20yaivrr1j.fsf@Sky.inp.nsk.su>
Lines:	32
X-Mailer:	Gnus v5.5/Emacs 19.34
Reply-To:	djgpp AT delorie DOT com

Daniel Barker <sokal AT holyrood DOT ed DOT ac DOT uk> writes:

> I have found it impossible to compile the GCC 2.8.1 source distribution
> under Windows 98 in one go. With the Windows 98 DPMI server, this seems to
> be due to DPMI selector leakage, as you suggest. If running from the BASH
> prompt, the build eventually fails with a load error. If running from the
> DOS prompt, the build eventually crashes when MS-DOS performs an illegal
> operation. 

I have a patch for make utility which adds workaround for this problem
in DPMI server.

http://www.jado.org/users/bukinm/misc/make.dif.gz

To build it, unzip make sources, apply the patch and follow
instructions in readme.dos file.

bash> unzip mak377s.zip
bash> gunzip -c make.dif.gz | patch -p1

Modified make utility is slower than original and it will not work
correctly for programs that want to allocate LDT descriptors and leave
them available even after finishing, but this is very unusual.

This is only partial workaround, because there are more programs that
may spawn other programs repeatedly, for example, bash and find.  But
I was unable to make resident utility that works around this problem
in DPMI server and does not require any changes in other programs (it
works, but is very unreliable).

-- 
Michael Bukin

- Raw text -