misc/111399: ghostscript-gpl WITH_FT_BRIDGE is defective

bf bf2006a at yahoo.com
Mon Apr 9 09:00:09 UTC 2007

>Number:         111399
>Category:       misc
>Synopsis:       ghostscript-gpl WITH_FT_BRIDGE is defective
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Apr 09 09:00:08 GMT 2007
>Originator:     bf
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
WITH_FT_BRIDGE=yes on 6.2-Stable i386, gv fails

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  
Dictionary stack:
   --dict:1087/1123(G)--   --dict:0/20(G)--  
--dict:74/200(L)--   --dict:1087/1123(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.



More information about the freebsd-bugs mailing list