Yes it’s known. I am already looking into it and told tb@ I would patch out the usage of dot(1) if I cannot find the underlying issue by the end of this week. It’s easy to reproduce just create an empty dir under /usr/local/share/fonts/. The issue comes from fontconfig somewhat.
— Antoine > On 20 Jul 2022, at 20:10, Christian Weisgerber <na...@mips.inka.de> wrote: > > From time to time, random ports fail with an error like this > (graphic/evince,light in this case): > > [229/306] /usr/local/bin/gi-docgen generate --quiet --fatal-warnings > --config=help/reference/libdocument/libevdocument.toml > --output-dir=help/reference/libdocument/libevdocument --no-namespace-dir > --content-dir=/usr/obj/ports/evince-42.3-light/evince-42.3/help/reference/libdocument > libdocument/EvinceDocument-3.0.gir > FAILED: help/reference/libdocument/libevdocument > /usr/local/bin/gi-docgen generate --quiet --fatal-warnings > --config=help/reference/libdocument/libevdocument.toml > --output-dir=help/reference/libdocument/libevdocument --no-namespace-dir > --content-dir=/usr/obj/ports/evince-42.3-light/evince-42.3/help/reference/libdocument > libdocument/EvinceDocument-3.0.gir > WARNING: Unable to process dot data: b'Fontconfig error: No writable cache > directories\n' > ninja: build stopped: subcommand failed. > > Can somebody please look into that? > > -- > Christian "naddy" Weisgerber na...@mips.inka.de >
