Re: pkg/52190: building graphics/cairo doesn't find ft2build.h

[David Holland <dholland-pbugs%netbsd.org@localhost>]

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

From: David Holland <dholland-pbugs%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/52190: building graphics/cairo doesn't find ft2build.h
Date: Sat, 5 May 2018 22:50:42 +0000

 On Tue, May 01, 2018 at 07:45:01PM +0000, Frank Wille wrote:
  >>  So, that apparently comes from freetype2's builtin.mk.
  >>  
  >>  When some builtin.mk fails to do its thing, the first thing to check is:
  >>     % make show-var VARNAME=IS_BUILTIN.freetype2
  >  
  >  "yes"
  >  
  >>     % make show-var VARNAME=USE_BUILTIN.freetype2
  >  
  >  "no"
  >  
  >  
  >>  If IS_BUILTIN is no, then the question is why it's not finding it; if
  >>  USE_BUILTIN is no, the question is why it's rejecting it.
  >  
  >  Good question. Any ideas how to debug that further?
 
 It is almost always a giant pain.
 
 (1) Check the value of BUILTIN_PKG.freetype2, which includes the
 version that builtin.mk thinks it's found. Compare this to
 BUILDLINK_API_DEPENDS.freetype2. If it's too low, you need to figure
 out if that's a real problem (in which case you effectively can't use
 the native version, but pkgsrc ought to build the pkgsrc version for
 you, and I'm not sure why that's not happening) or if builtin.mk is
 generating rubbish. On current I get freetype2-2.6.3 and in cairo at
 least the requirement is >= 2.4.5.
 
 (2) Check if freetype2 appears in FORCED_PKGSRC, which is the list of
 packages for which the builtin version is itself ok but the package
 depends on something that needs to come from pkgsrc. If it's in there,
 the variable FORCED_PKGSRC_REASONS (which I added recently and may not
 be in the stable branch, I forget) will tell you which package
 triggered it. This shouldn't be happening because freetype2 doesn't
 depend on anything but zlib, but...
 
 (3) Make sure PREFER.freetype2 didn't somehow get set to "pkgsrc".
 
 AFAICR that should cover the possibilities...
 
  >  >  Also, check to make sure that X11BASE is set correctly...
  >  
  >  I'm not sure how to do that. I have never set X11BASE on any NetBSD system
  >  in the past when compiling pkgsrc. And I always use the built-in Xorg, not
  >  the pkgsrc one.
 
 make show-var VARNAME=X11BASE
 
 if you haven't done anything it should be /usr/X11R7, but if for some
 reason it's not that would explain a lot of weirdness.
 
 BTW, it looks like the pkgconfig fixup thing you mentioned earlier is
 failing only because x11-links isn't providing the freetype2 links,
 and if we can fix that it should resolve itself.
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost