Re: pkg/48742: Building fontconfig fails with undefined reference to FcDirCacheRescan

["Ian D. Leroux" <idleroux%fastmail.fm@localhost>]

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

From: "Ian D. Leroux" <idleroux%fastmail.fm@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: David Holland <dholland-pbugs%netbsd.org@localhost>, 
pkg-manager%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost, pkgsrc-bugs%netbsd.org@localhost
Subject: Re: pkg/48742: Building fontconfig fails with undefined reference
 to FcDirCacheRescan
Date: Mon, 9 Jun 2014 12:14:03 +0200

 > From: David Holland <dholland-pbugs%netbsd.org@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: 
 > Subject: Re: pkg/48742: Building fontconfig fails with undefined
 > reference to FcDirCacheRescan
 > Date: Sat, 7 Jun 2014 21:03:49 +0000
 > 
 >  On Sun, Apr 13, 2014 at 02:45:00PM +0000, idleroux%fastmail.fm@localhost 
 > wrote:
 >   >   CCLD     fc-cache
 >   > fc-cache.o: In function `scanDirs':
 >   > fc-cache.c:(.text+0x1f7): undefined reference to
 >   > `FcDirCacheRescan' Makefile:474: recipe for target 'fc-cache'
 >   > failed gmake[2]: *** [fc-cache] Error 1
 >  
 >  This is caused by mixing native and pkgsrc X. Don't do that...
 
 As far as I know, I run strictly native X, and I ran into this in a
 freshly created pkg_comp chroot so there shouldn't have been any cruft
 from past mistakes lying around.  As I see it, there are two
 possibilities: Either fonts/fontconfig is only useful with modular X
 and it had no business being built on my native-X system, or
 fonts/fontconfig is (potentially) useful with native X.
 
 If pkgsrc fontconfig is not meant to be used with native X, then I'm
 perplexed that it got pulled in as a dependency while building
 packages for native X.  I think I was trying to build firefox24 when I
 first tripped over this, back in April.  However, I've just
 successfully built all the packages I care about from a pkgsrc tree
 checked out yesterday (2014-06-08) and fontconfig was not required, so
 if there was a bug in the dependencies it's gone now.  In this case we
 can close the PR.
 
 If pkgsrc fontconfig is expected to build on a native-X system, then we
 still have a bug that I can reproduce in a fresh pkg_comp chroot, with
 nothing in /etc/mk.conf beyond what pkg_comp puts there itself.  The
 bug doesn't affect me personally, but since I can reproduce it
 systematically I'm happy to help investigate if anyone else cares about
 it.
 
 Is there currently a mechanism for indicating or even enforcing that
 certain packages are modular-X-only?  In some cases its obvious, but
 for something like fontconfig (whose DESCR explicitly states that it is
 independent of X), it's not.
 
 --
 IDL