ports/179236: Build failure (lib-depends) for net/tigervnc when HPJPG is enabled

Scot Hetzel swhetzel at gmail.com
Mon Jul 1 07:10:01 UTC 2013


The following reply was made to PR ports/179236; it has been noted by GNATS.

From: Scot Hetzel <swhetzel at gmail.com>
To: bug-followup at FreeBSD.org, kevinz5000 at gmail.com
Cc: ports at freebsd.org
Subject: Re: ports/179236: Build failure (lib-depends) for net/tigervnc when
 HPJPG is enabled
Date: Mon, 1 Jul 2013 02:08:07 -0500

 On Sun, Jun 30, 2013 at 10:06 PM, Koichiro IWAO <meta+ports at vmeta.jp> wrote:
 > Would anyone mind taking ports/179236?
 >
 > ports/179236: Build failure (lib-depends) for net/tigervnc when HPJPG is
 > enabled
 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/179236
 >
 That fix is only covering up the problem.  You still won't be able to
 make a package of tigervnc with libjpeg-turbo (HPJPG) as a dependency
 on poudriere.
 
 The correct fix would be to find all ports that are installing
 graphics/jpeg and add an option to them to build with
 graphics/libjpeg-turbo instead.  This way poudriere would then be able
 to create packages linked to the appropriate port (graphics/jpeg or
 libjpeg-turbo).
 
 I looked at the build log, and it looks like the jasper package is the
 one that is installing graphics/jpeg.  To fix graphics/jasper, remove
 the LIB_DEPENDS line for graphics/jpeg from the Makefile.  Add HPJPG
 to OPTIONS_DEFINE, along with the description:
 
 HPJPG_DESC=             Build with High-Performance JPEG support
 
 Then below the '.include <bsd.port.options.mk>' line add the following:
 
 .if ${PORT_OPTIONS:MHPJPG}
 LIB_DEPENDS+=   turbojpeg:${PORTSDIR}/graphics/libjpeg-turbo
 .else
 LIB_DEPENDS+=   jpeg:${PORTSDIR}/graphics/jpeg
 .endif
 
 This should fix the jasper port.  Then try a poudriere run to see if
 jasper will build with the HPJPG option enabled.
 
 Note: you might find other ports/packages that have a dependency on
 graphics/jpeg that will need a similar fix.
 
 -- 
 DISCLAIMER:
 
 No electrons were maimed while sending this message. Only slightly bruised.


More information about the freebsd-ports-bugs mailing list