Re: [gentoo-user] Error with infinality font while emerging sane-backends

[Danny YUE]

On 2018-03-28 14:55, Floyd Anderson <f.a@××××.net> wrote:
> On Wed, 28 Mar 2018 13:58:21 +0800
> Danny YUE <sheepduke@×××××.com> wrote:
>>
>>
>>Thanks for your quick reply :-)
>>
>>I created the symbolic link as you told,
>
> That solves the:
>
> 	Fontconfig error: failed reading config file
> 	Fontconfig error: Cannot load config file "infinality/conf.d"
>
> errors – they’re gone.
>
>>but it still does not
>>work...same error message.
>
> Now you have to solve the:
>
> 	Error: /invalidfont in /findfont
>
> 	Last OS error: No such file or directory
> 	GPL Ghostscript 9.21: Error: /invalidfont in /findfont
>
> errors. The culprit seems here the Type-1 font selection, see bug
> #620148 [1]. Commenting the mentioned section in:
>
>    /etc/fonts/infinality/infinality.conf
>
> works here, bumping Ghostscript to version 9.23 doesn’t.
>
> Hope that helps. If not, you probably can temporarily rename:
>
>    /usr/bin/fig2dev (package media-gfx/transfig)
>
> to hide it from the media-gfx/sane-backends build process, so it wont build
> the PDF documentation. Previously sane-backends-1.0.27 compiles fine without
> media-gfx/xfig and therefore media-gfx/transfig.
>
>
> Reference:
>  [1] <https://bugs.gentoo.org/show_bug.cgi?id=620148>

Oops, I did not really see this email last week...my stupidity.

Thank you so much Floyd, you solved my problem perfectly.

After commenting out the section, the font problem never appeared any
more.

However the PDF file still refuses to build.
I knew the solution: disable parallel compilation feature.

After that it worked.

Thanks again!

Danny