Date: Mon, 10 Apr 1995 19:13:02 +0300
From: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
To: djgpp AT sun DOT soe DOT clarkson DOT edu, P DOT Taylor AT alpha1 DOT rhbnc DOT ac DOT uk
Subject: Re: LIBGRX
Cc: CHAA006 AT alpha1 DOT rhbnc DOT ac DOT uk

> 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 DJGPP GCC. 
> 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

If you *really* need to be able to recompile GRX, then:

You need Borland's Make, but not Borland's C (of course).  The current version of
GRX was developed a long time ago, and thus with an old version of DJGPP, so as
you've discovered it won't compile out of the box under the current version.
I would suggest to convert the makefiles so they would be accepted by GNU Make
(it really shouldn't be so hard to do; if you are not sure about some obscure
Borland Make option, post to the list, there are a number of people which can
help).  In this way, you can later post the corrected makefiles so others could
benefit.  I would also suggets compiling with -Wall switch and treat any warning
as real problem which needs correction (because quite a few header files has
changed since then).

> 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, Borland Make is incompatible with DJGPP, as explained in the DJGPP FAQ
list, Section 6.13.