pkgsrc-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: pkg/55885 (Harfbuzz fails to compile)






On Sat, 19 Dec 2020 22:15:54 +0000 (UTC)
leot%NetBSD.org@localhost wrote:

> Synopsis: Harfbuzz fails to compile
> Can you please double-check which installation sets are installed
> by sharing the output of `echo /etc/mtree/set.*'?
> 

This is a premade -current bootable image from invisible.ca, so it might be an issue with their image than pkgsrc. As X was pre-installed. So I guess, there is conflicts with what they built X with and the version of pkgsrc I'm using. 

Output is as follows: 

/etc/mtree/set.base /etc/mtree/set.comp /etc/mtree/set.dtb /etc/mtree/set.etc /etc/mtree/set.games /etc/mtree/set.man /etc/mtree/set.misc /etc/mtree/set.modules /etc/mtree/set.rescue /etc/mtree/set.tests /etc/mtree/set.text /etc/mtree/set.xbase /etc/mtree/set.xcomp /etc/mtree/set.xetc /etc/mtree/set.xfont /etc/mtree/set.xserver


> Can you please also share the package version of harfbuzz (that fails
> to install) and x11-links for completeness?
> 

Since submitting the issue for harfbuzz, the same issue popped up in a couple other libraries. So I imagine it's an issue with x11-links. It's been a long time since I used pkgsrc, so I am not completely familiar with how it works. I am assuming ".x11-buildlink" is pulls files locally, probably from x11-links, correct? 

So I dumped the files into /usr/pkgsrc/pkgtools/x11-links/work/share/x11-links/include/freetype2/freetype/config and that didn't fix the issue either. I also found a /usr/pkg/share/x11-links folder, dumped the files there, and still failed. Any ideas where I should put these files for a hack fix?


Anyway, the question you asked:
pkg_info harfbuzz = 2.7.2
pkg_info x11-links = 1.31

It also failed on Cairo and Pango, and one would assume it will fail anywhere else that links freetype2 via x11-links.

Looks like there was an update to x11-links. But cracking open the tgz file, it's missing the headers as well in the share folder.



Anyway, hope that helps. It's not a major issue for me. But I don't know if it affects anyone else, or just something I did stupidly. 

-- 
Eric <admin%ventdev.com@localhost>
Visual Entertainment and Technologies, LLC


Home | Main Index | Thread Index | Old Index