[Slackbuilds-users] tightvnc compile problems
andreas.guldstrand at gmail.com
Fri Jan 13 02:46:17 UTC 2017
Would be better to simply change the slackbuild script's make
invocation to make it -j 1 instead ... if that's done sbotools won't
try to use its -j setting
On 13 January 2017 at 02:31, Jim Diamond <Jim.Diamond at acadiau.ca> wrote:
> On Fri, Jan 13, 2017 at 08:17 (+0700), Willy Sudiarto Raharjo wrote:
>>> Thanks for the suggestions.
>>> (1) The sum checks out.
>>> (2) And I have
>>> in my copy of slackware, and dir /var/log/packages/xorg-* says
>>> So that all looks OK.
>> It it possible to attach the complete build log?
> It is. And I still can, if you want (just let me know).
> But it occurred to me that perhaps this is one of those packages that
> won't build if you give -j <something bigger than 1> as a make option.
> So I tried with -j 1
> sboconfig -j 1 ; sboinstall tightvnc
> And it worked this time.
> (If God didn't want me to have 8 compiles going at one time, He
> wouldn't have let me have a computer with 4 hyper-threaded cores.)
> So maybe I should rephrase my issue here as follows:
> Should we put a note in the README that says to use "-j 1" for
> best results?
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
More information about the SlackBuilds-users