From: kunst AT prl DOT philips DOT nl
Subject: Re: LIBGRX
To: P DOT Taylor AT alpha1 DOT rhbnc DOT ac DOT uk
Date: Mon, 10 Apr 1995 17:22:10 +0100 (METDST)
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu (DJGPP users list)

Philip Taylor writes:
> 
> Could anyone please tell me the status of LIBGRX?  As a DJGPP beginner, I am
> confused by the apparent conflicts which occur in LIBGRX.  The documentation
> for V1.03 refers to an imminent release of V1.04, but Archie has so far been
> unable to locate a copy of the latter, yet V1.03 appears to date back to 1993 
> (or so it would seem). In addition I am very confused by the apparent need for
> a non- DJGPP `C' compiler: the `MAKEFILE' referred to in the LIBGRX
> documentation appears not to exist, but there is a MAKE.BAT which presumably
> takes its place; however, the format of the MAKEFILEs which it slaves is not
> compatible with the DJGPP MAKE, in that it uses (for example) "!if $d(DEBUG)"
> where (I think) DJGPP MAKE would have "ifdef DEBUG", and some of the MAKEFILEs
> which it invokes are specifically for TCC (Turbo C?) rather than for DJGPPGCC.
> I would dearly like to be able to re-generate the LIBGRX files, so that I can
> start investigating my problems with VESADRV.VDR, but I am confused as to
> whether I simply have an out-of-date LIBGRX or whether there really is a need
> for Borland/Turbo MAKE & C and for DJGPP MAKE & C. I would be very grateful if
> a more knowledgable reader could clarify, and if there really is a need for
> Borland/Turbo MAKE & C, to let me know which version is needed, since my
> attempts to use a recent Borland MAKE failed: I first had to install a Borland
> DPMI server before it would function at all, and then found that DJGPP GCC
> locked up when fired up via Borland's MAKE+DPMI. 
> 

Yes, you'll need a copy of Borland Turbo C MAKE.EXE with these Makefiles.
To avoid the DPMI problems, use the REAL MODE version of MAKE.EXE: MAKER.EXE. 
You could rename MAKE.EXE to MAKEP.EXE and MAKER.EXE to MAKE.EXE.

DJGPP without a graphics driver specified uses the built-in VESA driver.
This one should work if your graphics card supports VESA (most do).
Otherwise get UNIVBE from Simtel.

Pieter.