Message-Id: <199807130150.CAA24788@sable.ox.ac.uk> Comments: Authenticated sender is From: George Foot To: Eli Zaretskii Date: Mon, 13 Jul 1998 02:47:35 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: djgpp alpha 980628 Reply-to: george DOT foot AT merton DOT oxford DOT ac DOT uk CC: djgpp-workers AT delorie DOT com Precedence: bulk On 5 Jul 98 at 15:50, Eli Zaretskii wrote: > For the record: I tried this on Windows 95. I used Windows 98, after applying most of the patches sent so far. > - If rebuilding libc indeed requires stubediting make.exe, how about > doing it automatically as part of the procedure? Does it require that? I didn't need to; but I'm using an old Make (3.7.5). > - "Load error: no DOS memory" when compiling posix/unistd/execlp.c > (typing "make" after that picks up where the previous one left > off). Seems like Windows 95 DPMI host is leaking DOS memory. > Suggest to mention that in the instructions. On one build, I received "Load error: can't switch mode". Rerunning Make solved this, so it's probably the same problem with the DPMI host, or at least something similar. Where are the instructions you mention? I couldn't find any. I built it using v2.01, by creating a fresh djgpp directory, installing djlsr202 there and copying the include files from djdev202. It feels slightly awkward to me to have to get djdev when I'm just going to recreate most of its contents. I also copied in from my 2.01 installation lib/djgpp.djl and lib/libgcc.a (I hadn't applied your patch to make libgcc be found properly). I hope that was correct; it seemed to work. > - fsdb and stubedit emit warnings. I noticed quite a few isolated warnings from various files; if nobody else has fixed them by the time I get around to it then I'll send patches. -- george DOT foot AT merton DOT oxford DOT ac DOT uk