[Bug 229332] print/ghostscript9-agpl-base: opvp driver is missing

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Jun 25 09:26:14 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229332

            Bug ID: 229332
           Summary: print/ghostscript9-agpl-base: opvp driver is missing
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: doceng at FreeBSD.org
          Reporter: omatsuda000 at gmail.com
             Flags: maintainer-feedback?(doceng at FreeBSD.org)
          Assignee: doceng at FreeBSD.org

The latest print/ghostscript9-agpl-base 9.23 doesn't include "opvp" driver,
which is a contributed one and, for example, used by some printer drivers such
as those for Canon printers.  Though the port is designed to include all
contributed drivers, "configure" script omit opvp driver from generated
Makefile as recorded in config.log: 

  WARNING: Unable to include opvp/oprp driver due to missing or disabled
prerequisites...

I couldn't understand why this happens. In "configure" there is a part as
follows: 

  if test x$ac_cv_lib_dl_dlopen != xno -a x$found_iconv != xno; then
            P_DEVS0="$P_DEVS0 $OPVP_DEVS"
  else
            { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: Unable to include
opvp/oprp driver due to missing or disabled prerequisites..." >&5 
  $as_echo "$as_me: WARNING: Unable to include opvp/oprp driver due to missing
or disabled prerequisites..." >&2;}
  fi

But this part is exacly the same as those for ghostscript9-agpl-base 9.16 which
successfully includes the opvp driver.

A bruteforce workaround is to modify Makefile by hand as follows:

  cd /usr/ports/print/ghostscript9-agpl-base
  make configure
  cd work/ghostscript9-agpl-base
  vi Makefile
  :   add the followin line
  :   DEVICE_DEVS8=$(DD)oprp.dev $(DD)opvp.dev
  cd ../..
  make

But obviously it cannot be a permanent solution...

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list