Re: pkg/48919

[David Sainty <dave%dtsp.co.nz@localhost>]

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

From: David Sainty <dave%dtsp.co.nz@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: Philip Miller <sighoya%gmail.com@localhost>, 
pkg-manager%netbsd.org@localhost, 
 gnats-admin%netbsd.org@localhost, pkgsrc-bugs%netbsd.org@localhost
Subject: Re: pkg/48919
Date: Fri, 04 Jul 2014 11:06:26 +1200

 On 04/07/14 05:30, Philip Miller wrote:
 > The following reply was made to PR pkg/48919; it has been noted by GNATS.
 >
 > From: Philip Miller <sighoya%gmail.com@localhost>
 > To: gnats-bugs%NetBSD.org@localhost, David Sainty <dave%dtsp.co.nz@localhost>
 > Cc:
 > Subject: Re: pkg/48919
 > Date: Thu, 03 Jul 2014 19:25:59 +0200
 >
 >   On 07/03/2014 07:00 AM, David Sainty wrote:
 >   > cat work/freetype-2.5.3/builds/unix/freetype2.pc
 >   With bmake clean before:
 >   
 >   prefix="/home/sighoya/pkg"
 >   exec_prefix="/home/sighoya/pkg"
 >   libdir="/home/sighoya/pkg/lib"
 >   includedir="/home/sighoya/pkg/include/freetype2"
 >   
 >   Name: FreeType 2
 >   URL: http://freetype.org
 >   Description: A free, high-quality, and portable font engine.
 >   Version: 17.2.11
 >   Requires:
 >   Requires.private: zlib
 >   Libs: -Wl,-R${libdir} -L${libdir} -lfreetype
 >   Libs.private: -lbz2
 >   Cflags: -I${includedir}
 >
 
 It looks right.  Are you able to check whether the installed 
 freetype2.pc also looks like this?
 
 And I guess then try clean+build in fontconfig - I know you've done 
 this, but I'm just thinking accidental stale build state might be 
 tripping us up.
 
 If fontconfig clean+build still fails for harfbuzz reasons, perhaps the 
 config.log from fontconfig might help (should be output somewhere in the 
 fontconfig work directory)...