Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: jaffe@elbereth.rutgers.edu (Saul Jaffe)
Newsgroups: comp.sys.sun
Subject: Re: Transcript under 4.0 ?
Keywords: Software
Message-ID: <204@brazos.Rice.edu>
Date: 14 Jul 89 15:35:38 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 32
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 75, message 7 of 15

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