[Slackbuilds-users] some SlackBuilds not respecting $MAKEFLAGS

[Jeremy Hansen]

>Some SlackBuilds aren't respecting $MAKEFLAGS!

Realistically, there is not a universal flag/environment variable you can
pass to every build system to limit the number of build processes. You'd
need to research individual build systems and see what they support.

>From my understanding, ninja does not support BUILDFLAGS, which means this
is not an SBo issue. Changes to the ninja build system seem to use
NINJAFLAG, so if you want to build the program one command at a time, you
should try passing `NINJAFLAGS="-j1"` to the SlackBuild or exporting it as
a system variable.

>It'd be nice if each SlackBuilds.org nodejs had a binary version.

Be the change you want in this world rather than seeking some rando to
conform and maintain your desires.

Jeremy



On Tue, Mar 10, 2026, 9:36 PM David Chmelik <dchmelik at gmail.com> wrote:

> Some SlackBuilds aren't respecting $MAKEFLAGS!  Ran a large 'queue'
> (weekly update of 200+ of about 1500+ installed, dependencies,
> rebuilds... sbocheck notifies of updates for bumps, objects, Perl,
> Python, Ruby, etc.) like  'MAKEFLAGS=-j1 sboupgrade <packages>' only for
> soon everything in X Window System (XFCE) to grind to a halt: ran out of
> RAM, and gcc/cc1plus running 32 jobs!  I double-checked another day;
> happened at least two or three times.  Hard to tell which but seems it
> was using ninja, and (after being forced to SSH in as root to kill
> sboupgrade) most recently modified were /tmp/SBo/*node*22*.  Are other
> arguments/flags/switches necessary like $MAKEFLAGS?  I don't know why
> nodejs would do this, but may not be the only SlackBuild not respecting
> $MAKEFLAGS.
>          I don't use nodejs22 personally, but it's a dependency of
> several SlackBuilds, and for several years has been halting
> sbopkg/sboinstall/sboupgrade due to running out of RAM (if I forget to
> set MAKEFLAGS=-j4, which slows down everything else that almost all
> finishes in good time with MAKEFLAGS=-j32) .
>          It'd be nice if each SlackBuilds.org nodejs had a binary
> version, and anything else needing high-end server-/workstation-size RAM
> like this which most people may not have... nodejs eats my 72/128 GB
> that procps detects (kernel detects all) plus 44+ GB swap memory and
> increasing.  A few other large/similar ones I recall taking a large
> amount of time and possibly RAM are google-go-lang, pandoc (thanks for
> pandoc-bin), some newer wxwidgets... other people can probably think of
> a few more.  Really most/all the rest should have binaries also even if
> they respect $MAKEFLAGS.
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20260311/37f38410/attachment.htm>