[Slackbuilds-users] Fontforge build error; SlackBuilds-users Digest, Vol 150, Issue 4

sborg63 sborg63 at disroot.org
Wed Oct 3 18:58:25 UTC 2018

On Wed, 03 Oct 2018 18:19:57 +0000
slackbuilds-users-request at slackbuilds.org wrote:

> Date: Wed, 3 Oct 2018 11:19:54 -0700 (PDT)
> From: Rich Shepard <rshepard at appl-ecosys.com>
> To: slackbuilds-users at slackbuilds.org
> Subject: [Slackbuilds-users] Fontforge build error
> Message-ID: <alpine.LNX.2.20.1810031116230.8354 at salmo.appl-ecosys.com>
> Content-Type: text/plain; format=flowed; charset=ISO-8859-7

>   fontforge-20170731 built on my 14-2/x86 desktop but fails to
>   complete on the new 14-2/x86_64 box (with AlienBOB's multilibs
>  installed). 
> In file included from /usr/lib/glib-2.0/include/glibconfig.h:9:0,

With multilib you could get confusion between /usr/lib
and /usr/lib64. Maybe it should be looking in /usr/lib64.

Have you considered this: https://www.slackbuilds.org/faq/#multilib

Plus, if the new box is the latest of the latest hardware-wise, it is
maybe worth considering running current because of its more 'current'
kernel. I had to do this whenever I got a new laptop;  the hardware was
much better supported as well as more recent software (the openblas
thread springs to mind).



More information about the SlackBuilds-users mailing list