🚀 go-pugleaf

I did this for hours and hours when I was porting TeX to my AViiON. It is
a subtle and creepy error. What is actually happening is this:

   On your aviion in the /usr/include directory there is a file named
   memory.h which is included by /usr/include/string.h

   In your TeX source directory there is a file named memory.h which
   TeX is using for soemthing or other.

   The TeX Makefiles run the compiler with lots of -I flags telling the
   preprocessor where to find things.

   The preprocessor winds up either getting /usr/include/memory.h where
   it expects the local memory.h or vice-versa (I forget which).

Personally, I was disgusted by DG referencing a non-standard header in
string.h, so I changed the /usr/include/string.h on my system to inline
expand the stuff it actually needed from memory.h.

If you aren't the sysadm of this DG system, you might have to do something
like make a local copy of the /usr/include/string.h file in the same directory
which already has the local copy of memory.h and fix your copy of string.h
to expand the stuff from /usr/include/memory.h

Good luck.
--
======================================================================
domain: tahorsley@csd.harris.com       USMail: Tom Horsley
  uucp: ...!uunet!hcx1!tahorsley               511 Kingbird Circle
                                               Delray Beach, FL  33444
+==== Censorship is the only form of Obscenity ======================+
|     (Wait, I forgot government tobacco subsidies...)               |
+====================================================================+