[SOLVED] unable to build qt5

USUARIONUEVO · 11-15-2019, 05:09 AM

Quote:

Originally Posted by nobodino

read carefully what I wrote.
I work with:
- slackware64-current
- plasma
- multilib,

and nothing else. no testing kernel.

And I try to rebuild plasma: SFS purpose.
qt5 is the first not building in the deps packages.
I have only 8 Go of RAM, is it suffisant?

If you try to build under "live" , no ... not suffisant... i remember some time try under my machine 16gb in live mode ... NO SPACE.

8GB in live , to build qt5 .... thats the problem.

nobodino · 11-15-2019, 06:07 AM

I don't build in live. My current system has been upgraded to plasma with kde removed as advised by Alien Bob.

Didier Spaier · 11-15-2019, 06:57 AM

Quote:

Originally Posted by nobodino

I have only 8 Go of RAM, is it suffisant?

No. For Slint I ended up building Qt 5.13.2 with a 32G swap file. Maybe an overkill, but 8G is certainly not enough. It at first failed to build on my laptop that has 8G RAM.

nobodino · 11-16-2019, 01:45 AM

I finally got it built, it was without X, in a lonely console. The limit is really above 8 Go.
A question: is there a way to limit the memory usage during the building of a package?

TheRealGrogan · 11-17-2019, 02:13 AM

One way to reduce memory usage for a build like that, would be to reduce the number of jobs. By default, ninja will use numprocs +2 so a quad core with hyperthreading would be -j10

Just add a -j value to the ninja command in your SlackBuild. e.g.

Code:

ninja -j4 -C builds/Release64

It will obviously take longer, but use less memory and run cooler.

Skaendo · 11-17-2019, 02:35 AM

Quote:

Originally Posted by Didier Spaier

For Slint I ended up building Qt 5.13.2 with a 32G swap file. Maybe an overkill, but 8G is certainly not enough. It at first failed to build on my laptop that has 8G RAM.

I have been building 5.13.1 with -j8, 8GB RAM and a 16GB Swap.

Skaendo · 11-17-2019, 02:39 AM

Quote:

Originally Posted by TheRealGrogan

Just add a -j value to the ninja command in your SlackBuild. e.g.

Code:

ninja -j4 -C builds/Release64

Would using

Code:

ninja -j4 -n5 -C builds/Release64

help any there (with ninja)?

TheRealGrogan · 11-17-2019, 04:45 AM

Quote:

Originally Posted by Skaendo

Would using

Code:

ninja -j4 -n5 -C builds/Release64

help any there (with ninja)?

Perhaps you mean -l5? That would limit the number of jobs according to load average. -n is "dry run"

Code:

[grogan@getstuffed:~]$ ninja --help
usage: ninja [options] [targets...]

if targets are unspecified, builds the 'default' target (see manual).

options:
  --version      print ninja version ("1.9.0")
  -v, --verbose  show all command lines while building

  -C DIR   change to DIR before doing anything else
  -f FILE  specify input build file [default=build.ninja]

  -j N     run N jobs in parallel (0 means infinity) [default=10 on this system]
  -k N     keep going until N jobs fail (0 means infinity) [default=1]
  -l N     do not start new jobs if the load average is greater than N
  -n       dry run (don't run commands but act like they succeeded)

  -d MODE  enable debugging (use '-d list' to list modes)
  -t TOOL  run a subtool (use '-t list' to list subtools)
    terminates toplevel options; further flags are passed to the tool
  -w FLAG  adjust warnings (use '-w list' to list warnings)

Skaendo · 11-17-2019, 05:09 AM

Quote:

Originally Posted by TheRealGrogan

Perhaps you mean -l5? That would limit the number of jobs according to load average. -n is "dry run"

Yep, you are correct. I was thinking -l. Don't know where I got n from.

nobodino · 11-24-2019, 02:26 AM

upgraded to 16 Go RAM this week end, qt5 builds fine now.