Summary: | media-libs/harfbuzz-6.0.0 - ../harfbuzz-6.0.0/meson.build:183:4: ERROR: Automatic wrap-based subproject downloading is disabled | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Mokrejš <mmokrejs> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Mokrejš
2023-02-24 05:48:23 UTC
Please always include emerge --info. Please also include /mnt/nocrypt/var/tmp/portage/portage/media-libs/harfbuzz-6.0.0/work/harfbuzz-6.0.0-abi_x86_64.amd64/meson-logs/meson-log.txt in this instance. Have you unmerged Harfbuzz or something, leading to a broken Cairo? Hi Sam, I unmerged harfbuzz to emerge it later again as it was causing dependency conflict. I wonder why configure fails badly if it cannot detect working cairo. It does not matter if it was working or broken, I cannot say from the emerge.log what was the culprit. Would the build.log point me to ${W}/harfbuzz-6.0.0-abi_x86_64.amd64/meson-logs/meson-log.txt I would look into it but I couldn't figure out where it was. Something what portage coud do and include in error messages. Still, if the cairo dependency is optional the configure check for it should not be fatal and harfbuzz be simply compiled without it's support. Isn't there a circular dependency between these two packages? Sorry that I do not ave the meson-log.txt, it got overwritten by the successfull compilation use USE=-cairo . I am not sure if it makes sense to reproduce the issue, supposedly by uninstalling some lib used by cairo lib. (In reply to Martin Mokrejš from comment #2) > Hi Sam, Hi > I unmerged harfbuzz to emerge it later again as it was causing dependency > conflict. 1. You should never need to unmerge anything. You should depclean things if they aren't needed anymore. If they are needed, you shouldn't need to remove them. It's a common misconception that one "needs" to. 2. You can't do this safely. For example, if Cairo is installed with Freetype support, then you unmerge Freetype, you leave Cairo's pkgconfig files (and libraries) broken, because they mention needing Freetype. Hence the error you got. > I wonder why configure fails badly if it cannot detect working > cairo. It does not matter if it was working or broken, No, it does matter. Another example of 2. above is bug 830044. Please read the discussion there, especially https://bugs.gentoo.org/830044#c7. > I cannot say from the > emerge.log what was the culprit. Would the build.log point me to > ${W}/harfbuzz-6.0.0-abi_x86_64.amd64/meson-logs/meson-log.txt I would look > into it but I couldn't figure out where it was. Something what portage coud > do and include in error messages. > > Still, if the cairo dependency is optional the configure check for it > should not be fatal and harfbuzz be simply compiled without it's support. > > Isn't there a circular dependency between these two packages? > Yes, but you had one installed with support for the other, then yanked it. You can't do that. |