* Make more use of makedep?
* The buildtemplates for as, c2, cc, ccom, cpp and ld seem to be sufficiently
  similar that it might almost be worth writing one parameterized template.
* What do we do with cgram.c?
* Have to be careful about choice and ordering of include files, esp. in unix
  version of ccom.  (Currently uses /usr/include/a.out.h or 
  /usr/sun/include/a.out.h [are they quite different?]) depending on ordering.
* There is far too much #ifdef UNIX stuff in the buildtemplates at present
  (my fault).  We could move it to the buildfiles that invoke the buildtemplate
  but I'm not wildly excited about that either - this way, at least all the
  confusion is in one place.
* The buildfiles and buildtemplates are in general still a little unsanitary.
* Unix version of as68 used to be linked with -g (include hooks for debuggers)
  I've taken this out - hope it doesn't matter.
* Does BOOTSTRAP really mean the same thing (and get used correctly) in all the
  source directories?
* Larger scale:
    - port size68, nm68, etc. to V
    - Currently, .b and unreversed b.out files are stored in VAX byte- and 
      bit-order.  Might be more sensible to convert as68, ld68 and sundry 
      tools to use 68000 order (i.e. rev68 output format).  For compatibility,
      could allow ld68 (and any tools that might be applied to .b files) to
      detect and deal with files in either format.  It's not just a difference
      of ordering: there are also differences in the size of a struct sym
      because of the differing ways that cc and cc68 align elements in
      structures.
