[Bug 206041] www/w3m GdkPixbuf not invoked - w3mimgdisplay broken

[bugzilla-noreply at freebsd.org]

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

            Bug ID: 206041
           Summary: www/w3m GdkPixbuf not invoked - w3mimgdisplay broken
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: nobutaka at FreeBSD.org
          Reporter: c.brinkhaus at t-online.de
          Assignee: nobutaka at FreeBSD.org
             Flags: maintainer-feedback?(nobutaka at FreeBSD.org)

Buiding the package with poudriere the log says
...
422 [pkg.esprimo.local] |  |  `-- Extracting jbigkit-2.1_1: .......... done
423 [pkg.esprimo.local] |  | `-- Extracting tiff-4.0.6: .......... done
424 [pkg.esprimo.local] |  `-- Extracting gdk-pixbuf2-2.32.1: .......... done
425 [pkg.esprimo.local] |  `-- Installing shared-mime-info-1.5...
...
533 checking if image is enabled... fb,x11
534 checking image library... gtk2
535 configure: WARNING: GdkPixbuf is not installed.  Install GdkPixbuf (version
>= 2.0.0)
536 configure: WARNING: unable to build w3mimgdisplay with X11 support
537 configure: WARNING: unable to build w3mimgdisplay with FB support
...
As the result w3mimgdisplay does not respond to commands as
echo -e '5;image.jpg\n' | /usr/local/libexec/w3m/w3mimgdisplay
which is the method to detect the image isze by py-ranger and my be others.

An extracted file from
http://distcache.freebsd.org/freebsd:10:x86:64/latest/All/
shows the similar behaviour. A build in a unclean environment finds GdkPixbuf.
This file responds to the example above.

A discussion about ranger is here
https://forums.freebsd.org/threads/ranger-file-manager-sysutils-py-ranger-on-freebsd.54513/

Thank you for your kind consideration!

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