Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!usc!bbn!gateway!TYCHO.NCSC.MIL!hsw
From: hsw@TYCHO.NCSC.MIL (Howard Weiss)
Newsgroups: comp.emacs
Subject: Re: Problems making uEmacs 3.10 on AOS/VS, VMS, DOS
Message-ID: <45742@bbn.COM>
Date: 18 Sep 89 19:32:00 GMT
Sender: news@bbn.COM
Organization: BBN news/mail gateway
Lines: 31


>From Richard Brown:
>- On VMS, there are numerous routines missing (such as getffile()).
>  I also get a lot of 'attribute conflict' errors in the link. I also
>  note that the ESTRUCT.H file requires one to set one of the various
>  C compiler flags to be non-zero, but there is no flag for VMS-C!!
 
If you read the section entitled Building MicroEMACS for VMS in the
emacs.txt file that comes as part of the distribution, it fills in the
details that you are missing.  I have just successfully compiled and am
running microEMACS 3.10 on VAX VMS 5.1.1.  I agree, the code could have
been a lot cleaner in the VMS area, and a .com file would have been nice,
but the price was right and I can't complain too much or too loudly.

In answer to you questions:

	getffile is not needed if you set COMPLET to 0 in estruct.h.
Completion does not work yet for VMS so you can either set COMPLET to 0 or
put in dummy functions for getffile and getnfile that do nothing.  The
attribute conflicts are in main - the conflicts are in epath.h and edef.h.
The compiler flags should all be 0.  I had to add another 0 switch to
estruct.h to satisfy the compiler for a stray #if.  Also, my VAX-C compiler
did not #if A | B types of constructs (most of these were #if BSD | V7,
etc).  By commenting out the or'd portion, the compiler was satified and
the code worked.  In order to compile I used the emacs.opt file as a guide
and used link emacs/option/share to link it all together.  Oh yea, char.obj
had to be added to emacs.opt to supply islower, isupper, etc.

Howard Weiss
hsw at tycho.ncsc.mil
-------