[Slackbuilds-users] Fontforge build error
dave at dawoodfall.net
Wed Oct 3 20:33:31 UTC 2018
On Wednesday 3 October 2018 12:58,
Rich Shepard <rshepard at appl-ecosys.com> put forth the proposition:
> On Wed, 3 Oct 2018, sborg63 wrote:
> > With multilib you could get confusion between /usr/lib
> > and /usr/lib64. Maybe it should be looking in /usr/lib64.
> This could be, but glib is found in /usr/lib64.
> > Have you considered this: https://www.slackbuilds.org/faq/#multilib
> Don't see anything applicable.
Try adding that under the CXXFLAGS= line in the slackbuild. It's
worth remembering as the first thing to try on a multilib system when
a build fails.
> > 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).
> I have been thinking this is an issue. In the past I've always built
> systems that were back from the bleeding edge. This time my budget allowed
> me to buy components near the top, but below the 'gamers' level. Since I'm
> getting build errors on packages that built with no errors on portables with
> 64-bit CPUs (but not the fastest, most expensive models) the hardware
> newness might well be the factor.
> I'll look into upgrading to current.
A physicist is an atom's way of knowing about atoms.
-- George Wald
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 801 bytes
Desc: not available
More information about the SlackBuilds-users