Bug 111399 - print/ghostscript8 (was ghostscript-gpl): WITH_FT_BRIDGE is defective
Summary: print/ghostscript8 (was ghostscript-gpl): WITH_FT_BRIDGE is defective
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-09 10:00 UTC by bf
Modified: 2015-09-16 23:31 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bf 2007-04-09 10:00:08 UTC
When ghostscript-gpl is built WITH_FT_BRIDGE=yes, 
which has also caused problems in
the past with other versions of ghostscript,  it seems
that either the freetype bridge code is defective,
improperly configured/built, or incompatible with the
older version of freetype 2 in our ports system. 

For example, when attempting to view a variety of postscript
files with the recent ghostscript-gpl built from the ports
system WITH_SVGALIB=yes WITH_SHLIB=yes
WITH_FT_BRIDGE=yes on 6.2-Stable i386, gv fails
with: 

While reading gs_fapi.ps:
Error: /undefinedfilename in (FAPIconfig)
Operand stack:
   (gs_fapi.ps)   2   Config   --nostringval--
Execution stack:
   %interp_exit   --nostringval--   --nostringval-- 

--nostringval--   %array_continue   --nostringval-- 

--nostringval--   false   1   %stopped_push  
--nostringval--
Dictionary stack:
   --dict:1087/1123(G)--   --dict:0/20(G)--  
--dict:74/200(L)--   --dict:1087/1123(G)--  
--dict:2/15(G)--
Current allocation mode is global
Last OS error: 2
Current file position is 1974
 
Error: PostScript interpreter failed in main window.
 
and ggv fails with:
 
File is not a valid PostScript document.
 
diff(1) reveals that my gs_fapi.ps is identical with
the most recent corresponding file in the
ghostscript cvs repository at the time I checked, 
with the exception of the $Id line. 
The errors persist after rebuilding all three ports.
Comment 1 Remko Lodder freebsd_committer freebsd_triage 2007-04-09 10:02:03 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-ports-bugs

Reassign to ports team.
Comment 2 Martin Wilke freebsd_committer freebsd_triage 2007-07-06 19:50:00 UTC
State Changed
From-To: open->feedback

Hi, 

The problem sill exists with the last Version of Portstree? 

- Martin
Comment 3 bf 2007-09-13 11:57:36 UTC
Martin:

Sorry about the delay in replying.  Yes,
unfortunately, the problem still exists with the
latest versions of the ports at the time I am writing
this.  I see from the ghostscript changelog that the
ghostscript maintainers have been working on some
related problems.  I don't know if the problem is due
to changes in freetype2 itself (the ghostscript
documentation suggests that they were working with an
earlier version of freetype2 than is in our ports
system).  The error message I receive now when
attempting to run ghostscript executables from the
command line is:

GPL Ghostscript 8.60 (2007-08-01)
Copyright (C) 2007 Artifex Software, Inc.  All rights
reserved.
This software comes with NO WARRANTY: see the file
PUBLIC for details.
While reading gs_fapi.ps:
Error: /undefinedfilename in (FAPIconfig)
Operand stack:
   (gs_fapi.ps)   2   Config   --nostringval--
Execution stack:
   %interp_exit   --nostringval--   --nostringval--  
--nostringval--   %array_continue   --nostringval--  
--nostringval--   --nostringval--   false   1  
%stopped_push   --nostringval--
Dictionary stack:
   --dict:1085/1123(G)--   --dict:0/20(G)--  
--dict:74/200(L)--   --dict:1085/1123(G)--  
--dict:2/15(G)--
Current allocation mode is global
Last OS error: 2
Current file position is 1984


I should also mention that the configure script that
is intended to add device drivers to the ghostscript
installation causes dialog(1) to dump core on my
computer, with the error message: "dialog: stack
overflow in function main", when I use the default
choices for the drivers (even when I'm not building
the freetype bridge).  I don't think that this is
related to ports/113144; it may be due to the fact
that I have the Propolice stack-smashing protector
patches on my system, and built all of my executables
with them.  In any event, it seems undesirable, and
perhaps the script should be altered: ports/113144
suggests that at least some changes are needed. 
However, when I've built ghostscript without the
freetype bridge it seems to work normally, and gs -h
yields:

GPL Ghostscript 8.60 (2007-08-01)
Copyright (C) 2007 Artifex Software, Inc.  All rights
reserved.
Usage: gs [switches] [file1.ps file2.ps ...]
Most frequently used switches: (you can use # in place
of =)
 -dNOPAUSE           no pause after page   | -q      
`quiet', fewer messages
 -g<width>x<height>  page size in pixels   | -r<res> 
pixels/inch resolution
 -sDEVICE=<devname>  select device         | -dBATCH 
exit after last file
 -sOutputFile=<file> select output file: - for stdout,
|command for pipe,
                                         embed %d or
%ld for page #
Input formats: PostScript PostScriptLevel1
PostScriptLevel2 PostScriptLevel3 PDF
Default output device: x11
Available devices:
   alc1900 alc2000 alc4000 alc4100 alc8500 alc8600
ap3250 appledmp atx23
   atx24 atx38 bbox bit bitcmyk bitrgb bj10e bj10v
bj10vh bj200 bjc600
   bjc800 bjc880j bjccmyk bjccolor bjcgray bjcmono
bmp16 bmp16m bmp256
   bmp32b bmpgray bmpmono bmpsep1 bmpsep8 ccr cdeskjet
cdj1600 cdj500 cdj550
   cdj670 cdj850 cdj880 cdj890 cdj970 cdjcolor cdjmono
cfax cgm24 cgm8
   cgmmono chp2200 cif cljet5 cljet5c cljet5pr coslw2p
coslwxl cp50 declj250
   deskjet devicen dfaxhigh dfaxlow dj505j djet500
djet500c dl2100 dmprt
   dnj650c epag epl2050 epl2050p epl2120 epl2500
epl2750 epl5800 epl5900
   epl6100 eps9high eps9mid epson epsonc epswrite
escpage faxg3 faxg32d
   faxg4 fmlbp fmpr fs600 gdi hl7x0 ibmpro ijs imagen
imdi inferno iwhi iwlo
   iwlq jetp3852 jj100 jpeg jpeggray la50 la70 la75
la75plus laserjet lbp310
   lbp320 lbp8 lex2050 lex3200 lex5700 lex7000 lips2p
lips3 lips4 lips4v
   lj250 lj4dith lj4dithp lj5gray lj5mono ljet2p ljet3
ljet3d ljet4 ljet4d
   ljetplus ln03 lp1800 lp1900 lp2000 lp2200 lp2400
lp2500 lp2563 lp3000c
   lp7500 lp7700 lp7900 lp8000 lp8000c lp8100 lp8200c
lp8300c lp8300f
   lp8400f lp8500c lp8600 lp8600f lp8700 lp8800c
lp8900 lp9000b lp9000c
   lp9100 lp9300 lp9400 lp9500c lp9600 lp9600s lp9800c
lq850 lvga256 lx5000
   lxm3200 lxm5700m m8510 mag16 mag256 md1xMono md2k
md50Eco md50Mono md5k
   mgr4 mgr8 mgrgray2 mgrgray4 mgrgray8 mgrmono miff24
mj500c mj6000c
   mj700v2c mj8000c ml600 necp6 npdl nullpage oce9050
oki182 oki4w okiibm
   oprp opvp paintjet pam pbm pbmraw pcl3 pcx16 pcx24b
pcx256 pcxcmyk
   pcxgray pcxmono pdfwrite pdfwrite permute pgm
pgmraw pgnm pgnmraw photoex
   picty180 pj pjetxl pjxl pjxl300 pkm pkmraw pksm
pksmraw plan9bm png16
   png16m png256 pngalpha pnggray pngmono pnm pnmraw
ppm ppmraw pr1000
   pr1000_4 pr150 pr201 ps2write psdcmyk psdrgb psgray
psmono psrgb pswrite
   pxlcolor pxlmono r4081 rpdl sgirgb sj48 spotcmyk
st800 stcolor sunhmono
   t4693d2 t4693d4 t4693d8 tek4696 tiff12nc tiff24nc
tiff32nc tiffcrle
   tiffg3 tiffg32d tiffg4 tiffgray tifflzw tiffpack
tiffsep uniprint vgalib
   wtscmyk wtsimdi x11 x11alpha x11cmyk x11cmyk2
x11cmyk4 x11cmyk8 x11gray2
   x11gray4 x11mono x11rg16x x11rg32x xcf xcfcmyk xes
Search path:
   . : /usr/local/share/ghostscript/8.60/lib :
   /usr/local/share/ghostscript/8.60/Resource :
   /usr/local/share/ghostscript/fonts
For more information, see
/usr/local/share/ghostscript/8.60/doc/Use.htm.
Please report bugs to bugs.ghostscript.com.









bf



--- Martin Wilke <miwi@FreeBSD.org> wrote:

> Synopsis: print/ghostscript-gpl: ghostscript-gpl
> WITH_FT_BRIDGE is defective
> 
> State-Changed-From-To: open->feedback
> State-Changed-By: miwi
> State-Changed-When: Fri Jul 6 18:50:00 UTC 2007
> State-Changed-Why: 
> Hi,
> 
> The problem sill exists with the last Version of
> Portstree?
> 
> - Martin
> 
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=111399
> 



       
____________________________________________________________________________________
Got a little couch potato? 
Check out fun summer activities for kids.
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
Comment 4 Rong-En Fan freebsd_committer freebsd_triage 2007-09-13 12:06:36 UTC
On Thu, Sep 13, 2007 at 03:57:36AM -0700, bf wrote:
> 
> I should also mention that the configure script that
> is intended to add device drivers to the ghostscript
> installation causes dialog(1) to dump core on my
> computer, with the error message: "dialog: stack
> overflow in function main", when I use the default
> choices for the drivers (even when I'm not building
> the freetype bridge).  I don't think that this is

This should be fixed in -STABLE branch some time ago.

Regards,
Rong-en Fan
Comment 5 Martin Wilke freebsd_committer freebsd_triage 2007-09-13 12:32:48 UTC
|> 
|> I should also mention that the configure script that
|> is intended to add device drivers to the ghostscript
|> installation causes dialog(1) to dump core on my
|> computer, with the error message: "dialog: stack
|> overflow in function main", when I use the default
|> choices for the drivers (even when I'm not building
|> the freetype bridge).  I don't think that this is
|
|This should be fixed in -STABLE branch some time ago.

Yep is already fixed.

- -- 
Martin Wilke            | irc.unixfreunde.de #bsd 
miwi@FreeBSD.org        | miwi@unixfreunde.de
FreeBSD Committer       | Power to Serve
Comment 6 Rong-En Fan freebsd_committer freebsd_triage 2008-01-12 13:48:15 UTC
Responsible Changed
From-To: freebsd-ports-bugs->rafan

I'll take it.
Comment 7 Rong-En Fan freebsd_committer freebsd_triage 2008-06-01 13:22:04 UTC
Responsible Changed
From-To: rafan->freebsd-ports-bugs

Back to pool.
Comment 8 Rong-En Fan freebsd_committer freebsd_triage 2008-06-01 14:40:26 UTC
Responsible Changed
From-To: freebsd-ports-bugs->doceng

Over to maintainer.
Comment 9 Pav Lucistnik freebsd_committer freebsd_triage 2008-11-12 16:15:50 UTC
State Changed
From-To: feedback->open

Feedback received some time ago
Comment 10 Carlo Strub freebsd_committer freebsd_triage 2014-08-29 20:09:01 UTC
doceng seems not to care about (not surprising, its a group so nobody might check PRs for doceng). Therefore, back to pool.