Arch Linux

TadaenSylvermane

Member

Registered: 2014-01-24

Posts: 34

Reason PKGBUILDs usually aren't multi core enabled?

I noticed this the other day and I checked the documentation, maybe I missed it.

When I do something from the AUR if there is a make process in the PKGBUILD it only does a single core. Is it expected to have a MAKEFLAGS set else is a reason they aren't something like this?

make -j $(nproc)

If I missed it forgive me. Curious to the reasoning as there are so few single core machines these days it seems a bit odd.

loqs

Member

Registered: 2014-03-06

Posts: 17,314

Re: Reason PKGBUILDs usually aren't multi core enabled?

See Makepkg#Building_optimized_binaries.

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,541

Re: Reason PKGBUILDs usually aren't multi core enabled?

Yes, you are expected to configure MAKEFLAGS. You set it to what you want, PKGBUILDs should not override that to use all cores. May people don't want it to use all cores.

JaydenDev

Member

Registered: 2022-07-11

Posts: 172

Re: Reason PKGBUILDs usually aren't multi core enabled?

While using all processor cores can sometimes double, triple, or quadruple compile times. It can bring your system to a screeching halt, and cause the system to be unusable. As it uses 100% on said amount of cores, it can make your system plain unusable for other tasks. And at the worst, freeze your system and prevent the compilation from continuing until you restart.

---

System Specs:
Intel Core i5-2400 Nvidia GTX 1050ti Logitech G402 Hyperion Fury (Mouse) BestBuy Essentials USB Keyboard
Software Specifications:
Desktop Environment: KDE Plasma Window Manager: KWin Operating System: Arch Linux (btw)

TadaenSylvermane

Member

Registered: 2014-01-24

Posts: 34

Re: Reason PKGBUILDs usually aren't multi core enabled?

Been away for a few days. Thank you much for the explanation.