eho@confidence.princeton.edu (Eric Ho) (06/30/89)
Does anyone out there have Transcript (the latest version , still 2.1 ?) working under SunOS 4.0.1 ? My Transcript 2.1 barfed when compiling pscomm.c (actually, it barfed much earlier than that -- in the top-level Makefile giving the unknown -c flag to sed). I was compiling on a 4.0.1 sparc machine. Any pointers would be much appreciated. -- ** PLEASE send replies to eho@confidence.princeton.edu ** Eric Ho Cognitive Science Lab., Princeton University voice = 609-987-2819 (x2987) email = eho@confidence.princeton.edu eho@bogey.princeton.edu reagrds. -eric-
jaffe@elbereth.rutgers.edu (Saul Jaffe) (07/14/89)
In article <4221@kalliope.rice.edu> eho@confidence.princeton.edu (Eric Ho) writes: > Does anyone out there have Transcript (the latest version , still 2.1 ?) > working under SunOS 4.0.1 ? > > My Transcript 2.1 barfed when compiling pscomm.c (actually, it barfed much > earlier than that -- in the top-level Makefile giving the unknown -c flag > to sed). I was compiling on a 4.0.1 sparc machine. I was able to get Transcript 2.1 running under 4.0 fairly easily. As I remember, I too got bit by that bug until I realized that the new version of sed just didn't have the -c flag. I think all you have to do is edit the makefile(s) and remove the references to the -c flag. The other change you may need to make concerns the logging facilities you use and the setting of the VERBOSELOG flag. It used to be that lpd opened the logfile listed in printcap and reopened it as stderr. This meant that Transcript, when it wrote log messages to the file (if VERBOSELOG was set) used stderr and thus the messages appeared in the right place. The 4.0 version of lpd though does not do this. If you want to use this logging feature you have to set the Transcript variable JOBOUTPUT to point to the right place in either the psint.sh (one file for all the printers) or in the .options file (for each printer). I don't remember any other changes that needed to be done for 4.0. Saul Jaffe Rutgers University ARPA: Jaffe@elbereth.rutgers.edu UUCP: ...!rutgers!elbereth.rutgers.edu!jaffe
guy@uunet.uu.net (Guy Harris) (07/23/89)
>I was able to get Transcript 2.1 running under 4.0 fairly easily. As I >remember, I too got bit by that bug until I realized that the new version >of sed just didn't have the -c flag. If there is anybody out there familiar with a version of "sed" that *DOES* have a "-c" flag, could they please let the rest of us know about it? Neither of the two versions I know of derived from AT&T's original "sed", namely the System V and 4.xBSD versions, have any such flag. As far as I know, no version of "sed" ever distributed with SunOS had such a flag, either. Maybe Adobe's cooked up such a version of "sed", but if so and if they use it in their Makefiles they should either 1) distribute that version of "sed" or 2) stop using that flag.