HDTenEightyP/NetNews huggingface dataset:
From: rajeev@ncr-fc.ftcollins.ncr.COM (Rajeev Krishnamoorthy)
Subject: Ghostscript 2.4
Followup-To: comp.lang.postscript,gnu.ghostscript.bug
Reply-To: rajeev@ncr-fc.ftcollins.ncr.com
Organization: NCR MED, FT. Collins, CO. 80525  (303) 223-5100
Distribution: gnu
Date: Tue, 14 Apr 1992 15:04:32 GMT

Two questions:

1. GS 2.4 seems to displace output a little -- it's not a problem, but
	I have to insert a 0 50 translate line to make it come out right.
	Why does this happen?
2. I have a 386 and a HP Laserjet III. When Ghostscript is drawing
	on the screen it's fast, but when I redirect output to the 
	printer, it takes 2-3 minutes per page. Is this normal?

TIA, 

Rajeev Krishnamoorthy (rajeev@ncr-fc.ftcollins.ncr.com)


Newsgroups: gnu.ghostscript.bug
From: farkas@eecg.toronto.edu (Keith I. Farkas)
Subject: line rendering in ghostscript2.4
Organization: University of Toronto
Distribution: gnu
Date: Fri, 10 Apr 1992 15:51:06 GMT

Ghostscript 2.4 seems to have problems drawing simple lines like those part
of a box outline that surrounding a table, or a boarder around the outside of
a page. Ghostscript 2.3, on the other hand, correctly draws such boxes.

Is this problem a bug? a feature? Does anyone have a fix?


Many thanks

	-Keith
	

Newsgroups: gnu.ghostscript.bug
From: quanstro@stolaf.edu (goon)
Subject: gs2.4 bad dithering on Sun SPARC II 8bit cg6
Organization: St. Olaf College
Distribution: gnu
Date: Mon, 6 Apr 1992 10:36:49 GMT

I have been having some trouble with vastly sub-optmial dithering from
gs on 24bit color images to 8 bit displays. The symptoms are mostly
heavy banding and under-utilization of availiable colors.

What's the deal? Is this a known bug?

ewq
--
quanstro@stolaf.edu (goon@uni-paderborn.de)
Erik Quanstrom		 
St. Olaf College	 
Northfield MN, 55057.5 USA			 

Newsgroups: gnu.ghostscript.bug
From: andy@huey.jpl.nasa.gov (Andy Poulsen)
Subject: gs2.4 and epson driver, 8514 display
Organization: JPL Optical Interferometry Group, ...
Distribution: gnu
Date: Tue, 7 Apr 1992 05:09:35 GMT

Hello everyone,

I'm trying to run gs2.4 on my 486 with an ati ultra.  I've got an
okidata 390 (24 pin) which is epson lq compatible.  I can't get any
resolution higher than vga to work on my monitor (i've loaded the 8514
adapter prior to running gs), and the epson driver messes up.  

setup:  I set bgiuser=n.ibm8514  (n = 1 to 10, nothing works)
	
	Command line (for hardcopy): gs386 -sDEVICE=epson -r180x180 file.ps

any idea what's wrong here?  when i got gs2.3a there was something in
the docs about a fix for the epson driver.  is the problem still around
for it, or what's going on.

any help would be greatly appreciated!

Thanks in advance!

andy

--
andy poulsen                   *
jpl 169-214/pasadena, ca 91109 *      we engineers have a saying:  
(818) 354-8033                 *
andy@huey.jpl.nasa.gov         *    we may be dumb, but we're slow...
 

Newsgroups: gnu.ghostscript.bug
From: ghost@aladdin.COM (L. Peter Deutsch)
Subject: Blank Mathematica output from GS 2.4
Organization: GNUs Not Usenet
Distribution: gnu
Date: Tue, 7 Apr 1992 03:39:31 GMT

In <9204020049.AA12076@raisin-nut>
<1992Apr1.054446.16828@talon.ucs.orst.edu>, Russell Ruby writes:

> I just replaced our old ghostscript 2.2 with the new
> ghostview/ghostsript 2.4 combination from prep. ... Turns out it draws
> a blank page for postscript files generated from Mathematica 2.0 --> psfix
> The same files can be displayed without problem using our old version
> 2.2 ghostscript.

"Testing can never show the absence of bugs, only their presence."
	- E. W. Dijkstra

Ghostscript's clipping logic was completely rewritten from 2.3 to
2.4.  It now is correct conceptually (i.e., it intersects clipping
regions rather than just replacing them), but despite the best
efforts of several dozen beta testers, there were at least two
residual bugs.  I've found and fixed these, and the Mathematic output
now displays correctly.

The fixes will be in release 2.4.1, due out next week if not sooner.
Unfortunately, they're a little too complicated to post.

L. Peter Deutsch :: Aladdin Enterprises :: P.O. box 60264, Palo Alto, CA 94306
ghost@aladdin.com, ...decwrl!aladdin!ghost ; 415-322-0103 8-9 AM M-F/msg
	    "Implementation is the sincerest form of flattery."


Newsgroups: gnu.ghostscript.bug
From: mikew@hpwarga.wal.hp.com (Michael Williams)
Subject: Re: More HP/UX 7.05 gs2.4 problems
Organization: GNUs Not Usenet
Distribution: gnu
Date: Thu, 9 Apr 1992 05:58:22 GMT

> Here's another problem, not related to HP cc optimization:
> 
> > make
>         ./ccgs "cc  -O  -DSYSV -Wc,-Ns5000 -Wc,-Nw500" _temp_.c gdevmem1.c
> "gdevmem1.c", line 456: operands of + have incompatible types
> 
> It certainly doesn't look like there're any problems that wouldn't show up
> with any cc compiler.  Any suggestions?

Here is a summary of the problems I encountered when compiling the
GhostScript distribution on an HP 9000/720:

1 - gdevx.c:
   Problem: "attempt to redefine" error
   Solution: stat() macro expansions must be expanded by hand

2 - gstype1.c:
   Problem: symbol table overflow
   Solution: compile with "-Wc,-Nw8000" switch

3 - gxclist.c:
   Problem: C1 enternal error
   Solution: compile without "-O" switch

4 - gdevmem1.c: 457
   Problem: operands have incompatible types
   Solution: cast both to int

5 - _temp_ (makefile)
   Problem: bad switch, can't find libraries
   Solution:  Add a space after the "L" switch in XLIBDIRS= in
     the makefile; rename library paths

-- 
Michael B. Williams
Hewlett-Packard Company
Medical Products Group
Waltham, MA 02254                    Prodigy: Dumped it
(617) 290-3734                       CompuServe: 73667,3264
mikew@hpwalq.wal.hp.com              America Online: Mike W99


Newsgroups: gnu.ghostscript.bug
From: refling@sloth.eng.uci.edu (John P. Refling)
Subject: Helpful hint so you can compile 2.4 on DOS
Organization: University of California, Irvine
Distribution: gnu
Date: Tue, 7 Apr 1992 19:56:10 GMT

I just spent the last few days tyring to get ghostscript 2.4 to compile
on DOS with Borland C++.  After much frustration, I discovered that there
are some auxillary programs which involk command.com during the compilation.

If command.com is not in your path, the compilation will fail!

It would be great if this were mentioned in the documentation in the
future.
--
-----------
John Refling, refling@sloth.eng.uci.edu

Newsgroups: gnu.ghostscript.bug
From: konolige@ai.sri.com (Kurt Konolige)
Subject: Re: ghostview
Organization: SRI International, Menlo Park, CA
Distribution: gnu
Date: Mon, 6 Apr 1992 16:00:18 GMT

The systems people at my site tell me we have a modified version of
the X11 application libraries that was causing ghostview to use cycles
even when idle.  Works fine with the vanilla libraries.  Sorry for the
post, I should check things out more here before I go to the net.  And
thanks to all those who responded, it looks like real bugs will get
all the attention they need. 

-Kurt Konolige

Newsgroups: gnu.ghostscript.bug
From: explorer@iastate.edu (Michael Graff)
Subject: Ghostscriot 2.4 problem with 300dpi driver
Organization: Iowa State University, Ames IA
Distribution: gnu
Date: Tue, 14 Apr 1992 01:58:02 GMT

I'm working on a driver for a Xerox printer we have here at ISU.  I know the
driver (kinda) works (it generates images for most files) but Ghostscript 2.4
seems to die when running screen.ps (which comes with the source) using this
driver.

It displays fine on the screen (X11R4) but created the following traceback
when core was dumped:

>  0 memset.memset(0x0, 0x0, 0x1000ae37, 0x10017040, 0xa7b) ["../memset.s":88, 0
x461dd8]
   1 render_ht() ["gxht.c":281, 0x438d84]
   2 gx_color_load() ["gxht.c":209, 0x438a90]
   3 gs_fill_adjust() ["gspaint.c":58, 0x4289a0]
   4 gs_fill() ["gspaint.c":47, 0x428930]
   5 zfill() ["zpaint.c":47, 0x41be58]
   6 interp.interp() ["interp.c":535, 0x40523c]
   7 gs_interpret() ["interp.c":176, 0x4045ec]
   8 run_string() ["gs.c":314, 0x400b20]
   9 swproc() ["gs.c":146, 0x4003c4]
  10 gs_main() ["gsmain.c":111, 0x41d34c]
  11 main() ["gs.c":123, 0x4002b8]

Is this a known bug, or is it something only I've found?  ;)

Thanks,
--Michael

-- 
-------------------------------------------------------------------------------
Michael Graff     explorer@iastate.edu   gg.mlg@isumvs.bitnet    "VMS fornever"
My favorite quote:  "And then, 23$2 k523%K5 fm$#%2345 34f $#r43r 34f,
-------------------------------------------------------------------------------

Newsgroups: gnu.ghostscript.bug
From: ghost@aladdin.COM (L. Peter Deutsch)
Subject: Re: line rendering in ghostscript2.4
Organization: GNUs Not Usenet
Distribution: gnu
Date: Sat, 11 Apr 1992 13:49:47 GMT

Re <9204110609.AA10334@raisin-nut>
<92Apr10.195131edt.6866@jarvis.csri.toronto.edu>:

> Ghostscript 2.4 seems to have problems drawing simple lines like those part
> of a box outline that surrounding a table, or a boarder around the outside of
> a page. Ghostscript 2.3, on the other hand, correctly draws such boxes.
> 
> Is this problem a bug? a feature? Does anyone have a fix?

Since you don't say what you mean by "problems," I'll have to guess
that you mean that the lines sometimes don't appear.

It is a known problem that Ghostscript sometimes fails to draw
one-pixel-wide lines (currentlinewidth = 0).  I'm haven't decided yet
which of several ways to fix this.

There is also a bug that is specific to dvips output, which affects
lines of all thicknesses, but only on certain devices.  This shows up
because dvips uses the `image' operator to draw lines.  There is a
one-line fix for this bug: change line 280 (approximately) of
gsimage.c from
		  penum->unpack = image_unpack_8;
to
		  { penum->unpack = image_unpack_8;
		    penum->bps = 8;
		  }
This fix will be in release 2.4.1, planned for next week.

L. Peter Deutsch :: Aladdin Enterprises :: P.O. box 60264, Palo Alto, CA 94306
ghost@aladdin.com, ...decwrl!aladdin!ghost ; 415-322-0103 8-9 AM M-F/msg
	    "Implementation is the sincerest form of flattery."


Newsgroups: gnu.ghostscript.bug
From: ghost@aladdin.COM (L. Peter Deutsch)
Subject: Re: Dumb question: gs 2.4 chokes on .pfb's
Organization: GNUs Not Usenet
Distribution: gnu
Date: Thu, 16 Apr 1992 06:01:05 GMT

Re
<9204111911.AA11232@raisin-nut>
<THOMAS.92Apr11192817@sorley.cogsci.ed.ac.uk>:

> For what they are worth, here are some observations I made with
> respect to the problem, using the real mode MSDOS executable of
> Ghostscript2.4 (gs.exe):
> 
> (a) I printed a document to disk using the new Windows 3.1 PS driver.
> The driver downloads an error handler into the print-file which
> will print out stuff when things go haywire, e.g. when the interpreter
> can't successfully load the font file. Now, the interpreter has to
> print these messages and it does so (hold your breath) using the very
> same font it choked on.(??)
> 
> (b) While the interpreter rejects some (but not all) dubious converted
> binary font files, it will also barf at some (but not all) Adobe fonts
> (see first quote).
> 
> (c) The protected mode version of gs24 (gs386.exe) will load all of my
> fonts, _including_ those rejected by gs.exe with no problems at all.
> (I thought both versions used the same code, or do they?)  Alas,
> gs386.exe and Windows will not coexist (Unix people stop sniggering
> :-} ).

I suspect the following:

	- The non-386 version does not use extended or expanded
memory, and it typically runs out of memory at about 3 or 4 fonts.
If the error name is VMerror, that's what's happening.

	- There is a bug in the non-386 version which causes it to
get confused and mis-parse .PFB files if the eexec (encrypted
outline) portion of the file is longer than 32K bytes and shorter
than 64K bytes, or longer than 96K and shorter than 128K.  I suspect
a number of Adobe fonts have this property.  This bug will be fixed
in 2.4.1, scheduled for release on April 16.

L. Peter Deutsch :: Aladdin Enterprises :: P.O. box 60264, Palo Alto, CA 94306
ghost@aladdin.com, ...decwrl!aladdin!ghost ; 415-322-0103 8-9 AM M-F/msg
	    "Implementation is the sincerest form of flattery."


Newsgroups: gnu.ghostscript.bug
From: zavgren@doowap.ltn.dec.com (John Zavgren DTN 226-6646)
Subject: Ghostview file finder gets confused?? (VAXstation 3100 with UTWS4.2)
Reply-To: zavgren@school.enet.dec.com (John Zavgren 508-486-6646)
Organization: Digital Equipment Corporation
Distribution: gnu
Date: Fri, 10 Apr 1992 14:03:09 GMT

All:

 When I use ghostview, even in a directory with one and only one file, e.g.,
doc.ps, by executing the command: ghostview doc.ps, ghostview tries to
open the file doc.dvi. The file selection window claims that it tried to
open doc.ps, but the error message window claims that it tried to open doc.dvi.
I tried to work around the file finder by renaming doc.ps to doc.dvi and 
then opening doc.dvi but I still get an error message and the previewer 
doesn't work.

 I searched all the source files and there is no string "dvi" anywhere.

 I built the code on a VAXstation3100 that runs Ultrix4.2.

Weird huh?

RSVP John Zavgren
zavgren@school.enet.dec.com

Newsgroups: gnu.ghostscript.bug
From: neideck@kaputt.enet.DEc.COM (Burkhard Neidecker-Lutz)
Subject: Porting report GhostScript 2.4 to Ultrix 4.2
Organization: CEC Karlsruhe
Distribution: gnu
Date: Wed, 15 Apr 1992 09:44:13 GMT

I don't know whether that is a Ultrix header file bug...

In order to make GhostScript 2.4 compile on Ultrix 4.2A with the DEC C
ANSI compiler I had to change memory_.h because otherwise the prototypes
in /usr/include/memory.h wouldn't know what size_t is:

#      else
#        include <stddef.h>		<-- add this
#        include <memory.h>
#      endif

You may consider adding something along these lines (maybe conditional on
Ultrix) for easier building.

		Burkhard Neidecker-Lutz

Multimedia Engineering, CEC Karlsruhe
Software Motion Pictures
Digital Equipment Corporation
neidecker@nestvx.enet.dec.com

Newsgroups: gnu.ghostscript.bug
From: ghost@aladdin.COM (L. Peter Deutsch)
Subject: Re: Some problem in using MSDOS gs2.4: gs.exe and gs386.exe
Organization: GNUs Not Usenet
Distribution: gnu
Date: Sat, 11 Apr 1992 06:14:13 GMT

Re <9204110408.AA09971@raisin-nut> <19542@chopin.udel.edu>:

Boris Chang reports problems displaying PostScript files:

>    The (B) 8 bit color ps file could not displayed was
> 
>    %!PS-Abode-3.0 EPSF-3.0
>    %%BoundingBox 0 0 
>    %%LanaguageLevel: 2
>    %%EndProlog
>    320 200 scale 
>    [/Indexed /Device RGB 255
>    < .... (some color map data I guess) ...>
>    ] setcolorspace
>    <<
>    /ImageType 1
>    /Width 320 /Height 200
>    /BitsPerComponent 8
>    /Decode [0 1 0 1 0 1]
>    /ImageMatrix [320 0 0 -200 0 200] 
>    /DataSource Currentfile /ASCIIHexDecode filter
>    >>
>    image

setcolorspace, <<, >>, and the dictionary form of `image' are Level 2
PostScript features that Ghostscript does not currently implement.

> 3. The (A) file 24 bit color image also wouldn't work: (ps file)
>    
>    ......
>    320 200 scale
>    /picstr 960 string def
>    320 200 24
>    [320 0 0 -200 0 200] {currentfile ... pop}
>    false 3
>    colorimage
>    .... (color image data) ...
>    %%EOF
> 
>    The error message was:
>    ----------------------------------------------
>    Initializing... done.
>    Error: /rangecheck in --colorimage--
>    Operand stack:
>        320  200  24  [320 0 0 -200 0 200]  
>    {currentfile picstr readhexstring pop}  
>    false  3
>    Execution stack:
>        %interp_exit    --nostringval--  --nostringval--  false  
>    --nostringval--  --nostringval--  false  --nostringval--   
>    --nostringval--  --nostringval--
>    Dictionary stack:
>        426/449  6/200
>    Ghostscript 2.4 (3/25/92)
>    --------------------------------------------	
>    I do not know how to make it works!

This file is not valid, according to the specification of colorimage
on p. 376 of the PostScript Language Reference Manual, Second
Edition.  The value 24 is not legal as the bits/comp argument for
colorimage: this value must be the number of bits for each component,
not the total number of bits in each pixel.  In other words, this is
caused by a bug in the Alchemy program that produced the PostScript
file.

> 4. The gs386.exe (plus dos4gw.exe) was not functioned at all.  
>    The error message was: (after I execute gs386 myfile.ps)
> 
>    DOS/4GW Protected Mode Run-Time Version 1.3
>    Copyright ....
>    DOS/4GW Fatal error: Loader failed --LINEXE_LOADER
> 

Several other people have reported this error.  I do not know what it
means.  I cannot find it in the Watcom documentation.  I will report
it to Watcom Technical Support and post the reply here.

L. Peter Deutsch :: Aladdin Enterprises :: P.O. box 60264, Palo Alto, CA 94306
ghost@aladdin.com, ...decwrl!aladdin!ghost ; 415-322-0103 8-9 AM M-F/msg
	    "Implementation is the sincerest form of flattery."


Newsgroups: gnu.ghostscript.bug
From: mikew@hpwarga.wal.hp.com (Michael Williams)
Subject: Re: Re: More HP/UX 7.05 gs2.4 problems
Organization: GNUs Not Usenet
Distribution: gnu
Date: Mon, 13 Apr 1992 14:02:39 GMT

> > Here is a summary of the problems I encountered when compiling the
> > GhostScript distribution on an HP 9000/720:
> 
> Which version?

This refers to the officially released version of GhostScript 2.4, taken
directly from prep.ai.mit.edu.

> > 1 - gdevx.c:
> >    Problem: "attempt to redefine" error
> >    Solution: stat() macro expansions must be expanded by hand
> 
> These macros do not appear in the 2.4 distribution.  You must have
> somehow wound up with a pre-release version of 2.4.

You are correct; the above message actually occurred during compilation of
a pre-release version, since discarded -- my mistake.

> > 4 - gdevmem1.c: 457
> >    Problem: operands have incompatible types
> >    Solution: cast both to int
> 
> As I noted in a previous message, I believe both K&R and the ANSI
> standard allow what is in the code.

I believe you are correct; the cast was my best guess to get the code
to compile under HP-UX.

> L. Peter Deutsch :: Aladdin Enterprises :: P.O. box 60264, Palo Alto, CA 94306
> ghost@aladdin.com, ...decwrl!aladdin!ghost ; 415-322-0103 8-9 AM M-F/msg
> 	    "Implementation is the sincerest form of flattery."
> 

Michael B. Williams
Hewlett-Packard Company
Medical Products Group
Waltham, MA 02254                    Prodigy: Dumped it
(617) 290-3734                       CompuServe: 73667,3264
mikew@hpwalq.wal.hp.com              America Online: Mike W99

Newsgroups: gnu.ghostscript.bug
From: iversen@dsfys1.fi.uib.no (Per Steinar Iversen)
Subject: gs2image use?
Reply-To: iversen@vsfys1.fi.uib.no
Organization: Department of Physics, University of Bergen, Norway
Distribution: gnu
Date: Sat, 11 Apr 1992 11:40:40 GMT

I have to print a strange ps-file, it comes from an IBM VM system (much of the
file is in EBCDIC!) and it needs huge printer resources to print - Ghostscript
have no problems though. The ps2image.ps file might do the trick if I could
figure out how to use it - how can I convert a range of pages from the manual
to ps-bitimages? These would probably print, if slowly. How can I set the 
resolution to 300dpi, to match the printer? So far the main effect of ps2image 
is to scroll rapidly through the file, without any file output.

My hardware is a DECstation 5000/200 CX, the software Ultrix 4.2 and gs24.

-psi

+------------------------------------------------------------------------------+
! Per Steinar Iversen    ! Internet:     iversen@vsfys1.fi.uib.no              !
! Fysisk Institutt       ! BITnet:       iversen@cernvm.bitnet                 !
! Universitetet i Bergen ! HEPnet:       VSFYS::IVERSEN (VSFYS=21.341=21845)   !
! Allegaten 55           ! Phone:       +47 5 212770                           !
! N-5007 Bergen          ! Fax:         +47 5 318334                           !
! NORWAY                 !                                                     !
+------------------------------------------------------------------------------+

Newsgroups: gnu.ghostscript.bug
From: melennec@airbus.stna7.stna.dgac.fr (Ronan Melennec)
Subject: where can .afm files be found ?
Organization: Service Technique de la Navigation Aerienne, France
Distribution: gnu
Date: Thu, 16 Apr 1992 12:40:00 GMT

Hello,

This post is not about a bug, but rather about a would-be feature.

I would like to use certain fonts that are supplied with Ghostscript,
but I only found the corresponding .pfa or .gsf files. I also
need their metrics, in the form of .afm files (so I can use them
in a TeX document, for example ; I have the afm2tfm processor).

Would it be difficult or costly to include those .afm in the ghostscript
fonts distribution ? Meanwhile, could anybody point me to an FTP site
from where they could be downloaded ? For the time being, I'm
particularly interested in the Utopia family .afm files...

Please answer by e-mail to melennec@stna7.stna.dgac.fr ;
I will post a summary if requested.

Thank you in advance,

Ronan


Newsgroups: gnu.ghostscript.bug
From: datri@convex.com (Anthony A. Datri)
Subject: Re: gs2.4 bad dithering on Sun SPARC II 8bit cg6
Organization: Engineering, CONVEX Computer Corp., Richardson, Tx., USA
Distribution: gnu
Date: Wed, 8 Apr 1992 16:11:40 GMT

>I have been having some trouble with vastly sub-optmial dithering from
>gs on 24bit color images to 8 bit displays. The symptoms are mostly
>heavy banding and under-utilization of availiable colors.

>What's the deal? Is this a known bug?

If you're willing to better the X11 driver, I'm sure that ghostscript would
be happy to incorporate your code.  2.4 does a little better with colors than
2.3 does, and I'd say that it does at least as well as any PostScript printer
that I've seen.
-- 


======================================================8--<

Newsgroups: gnu.ghostscript.bug
From: thu@huedv.sta.SUb.ORG (Thomas Huppertz)
Subject: Re: How to Quit ?
Reply-To: thu@huedv.sta.sub.org
Organization: HUPPERTZ EDV-Beratung, Thererstr. 10, 8083 Mammendorf, Germany
Distribution: gnu
Date: Sat, 11 Apr 1992 20:59:16 GMT

xiaofei@acsu.buffalo.edu (XiaoFei Wang) writes:

>Ghostscript on PC: 

>After Printing a Postscript file using Ghostscript, it leaves:
>GS>
>and I have to type quit and then print the second file. 

>Suppose I have to print 10 files. I want to send a batch file and then
>go out to buy a coffee and then pick up the ten files, how can I do it?


Simply print *11* files - the last one is 'quit.ps'   :-)

-- 
==================== Gruss: === Thomas === Huppertz  ========================
       HUPPERTZ EDV-Beratung, Thererstr. 10, 8083 Mammendorf, Germany 
               Tel. ++49-8145-1569, Fax. ++49-8145-8286 
====== EMail:=== thu@huedv.sta.sub.org === (oder: huppertz@guug.de) =========

Newsgroups: gnu.ghostscript.bug
From: debra@wsinis07.info.win.tue.nl (Paul De Bra)
Subject: Re: Ghostview 1.1 released
Keywords: ghostscript preview X11
Reply-To: debra@info.win.tue.nl
Organization: Eindhoven University of Technology, the Netherlands
Distribution: gnu
Date: Mon, 6 Apr 1992 10:14:27 GMT

In article <1992Mar25.203908.4906@daffy.cs.wisc.edu> tim@cs.wisc.edu (Tim Theisen) writes:
>    Ghostview-1.1 is available via anonymous ftp from:
>	prep.ai.mit.edu:/pub/gnu/ghostview-1.1.tar.Z
>	appenzell.cs.wisc.edu:/pub/ghostview-1.1.tar.Z
> ...

Since there is no gnu.ghostview.bug group yet, i'll just mention the
following (minor) problems here:

I tried (and succeeded) compiling and running ghostview on sVr4 (386)
but only after correcting a few glitches:

1. The name "st_mtime" cannot be used with sVr4. The file <stat.h>
   redefines it as st_mtim.sec, not just in the stat structure, but
   simply by a #define, thus also applying to your own st_mtime fields.
 
   cure: rename st_mtime to something else.

2. In Path.c the function getuid is used which should be declared as
   returning the type uid_t (which happens to be long on sVr4-386)

3. The file setenv.c uses bcopy instead of memcpy.
   bcopy need not exist, memcpy should exist (but doesn't exist everywhere).
   a #define bcopy(a, b, c) memcpy(b, a, c) could cure this.

Otherwise ghostview works just fine on AT&T sVr4.0 (2.1) with x11r5.

Paul.

Newsgroups: gnu.ghostscript.bug