fmbutt@mrbt.sw.stratus.com (Farooq Butt) (07/30/90)
Guru(ette)s: I just recompiled the AT&T DWB 5.2 package on my SPARC machine and it is behaving verrrrrrrrrrry strangely. The results I see are weird binary control sequences in the ditroff output etc. [The ditroff output is supposed to be ASCII]. This leads me to immediately suspect that the (di)troff supplied with AT&T DWB 5.2 is HIGHLY machine/wordsize/endian dependent since it works just peachily on my 6080x0 machine. I took a look at the "tdef.h" include file and chills started shooting up my spine as I saw a morass of code that does not seem to have been touched since Dennis Ritchie was a boy. Questions: . Does anyone have a suggestion as to how I should go about getting this troff to work on my SPARC ? Deltafiles would we conveeeenient... Someone must have run into this with DWB 5.2... . Is there a nice, easy to install public domain type package that will do the job ? I am getting sick of hacking files with descriptive titles like "p0.c"....grrrrr... I would like the package to be a drop in replacement for the DWB (di)troff. (I say "di" because the DWB troff spews out ASCII, not C/A/T code). -- Hi-Tech Disclaimer: NOTHING in the above article has any relationship to reality. If any reality correspondences are found, please notify me IMMEDIATELY. Any threats or abuse of any kind is purely unintentional. My employer is not liable.
gwyn@smoke.BRL.MIL (Doug Gwyn) (07/30/90)
In article <1827@lectroid.sw.stratus.com> fmbutt@mrbt.sw.stratus.com (Farooq Butt) writes: >I just recompiled the AT&T DWB 5.2 package on my SPARC machine and ... This is the first I've heard of "DWB 5.2"; what is it? DWB 2.0 did contain several instances of improper use of argument lists instead of varargs, which cause porting problems; I fixed those long ago and can provide a copy to source licensees.