Two problems with fixinc.sh on SunOS4 ...

[Jeffrey A Law]

  In message < 199904050214.WAA29714@caip.rutgers.edu >you write:
  > 	The particular circumstances which tickled the /bin/find bug are
  > unlikely to occur on a normal system out of the box.  (E.g. normal
  > systems don't have long paths in /usr/include which then symlink
  > elsewhere to a long path.  Gcc will expand that into one long dir in
  > gcc/include.  This was a local hack done by my sysadmin for whatever
  > reason, and it tickled the bug in sun's /bin/find.)
It's not _that_ weird.  A typical 4.3/4.4 BSD system would have 
/usr/include/sys link into the kernel sources elsewhere on the system.

I thought some linux systems did similar things with /usr/include/asm and
other directories (linking to /usr/src/linux/include/asm-blah for example)

  > 	So no need to worry, IMO. 
Depends on what the real underlying problem was.  It's my job to worry :-)

  > PS: there was still one case of sed -e'blah' I noticed:
  > 
  >  > Fixed ./vfork.h:
  >  >       machine_name
  >  > sed: Unrecognized command: -e/define[   ]HUGE_VAL[      ]/a\
  >  > #endif
I think this one has been fixed.

Thanks,
jeff