Date: Thu, 10 Nov 94 06:16:39 JST
From: Stephen Turnbull <turnbull AT shako DOT sk DOT tsukuba DOT ac DOT jp>
To: TAUPIN AT rsovax DOT lps DOT u-psud DOT fr
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Trying to compile MicroEmacs

[Note to DT:  your mailer uses the abbreviation "Subj:" for
"Subject:"; my mailer doesn't recognize that which means I have to
retype subjects by hand....]

   Date:   9-NOV-1994 15:24:26 +0100
   From: TAUPIN AT rsovax DOT lps DOT u-psud DOT fr
   Subj:  Trying to compile MicroEmacs


   Following the suggestion of Aaron Ucho, I included sys/farptr.h in a
   ghostly mem.h.

   NNow, I get a lot of GCC diags with the "PASCAL NEAR" statements.

I think that these refer to calls to the operating system.  You can
probably just do

        #define PASCAL
        #define NEAR

in all the source files, since these functions will be handled by GO32
or the library as normal DJGPP functions.  If they aren't, you're
going to have to do a lot of recoding.  (The NEAR keyword you had
better be able to comment out.)
    Another possibility is that Pascal calling syntax is used for
efficiency reasons in MicroEmacs code itself.  Then there would be no
problem just turning them into nothing.
    Finally, microEmacs may be linked against a GNUish library written
in Pascal or assembler using Pascal conventions.  Big trouble....
    So I think you just start by #define'ing them away, and see what
happens.
    --Steve