openvix dev build instructions

[birdman]

nodejs and QT both peak over 24GB in my build.

I've just run a build from scratch (kept sources) of 6.2.002.004.
On a system with 8 CPUs and 16GB of memory the maximum memory usage, according to sar, was 80% and there is no sign of paging.

I just let it run with the standard CPU count setting, as since both bitbake and several (many?) of the individual builds all try to use all of the CPUs they are always well overcommitted (my run-q size hovers around 40 and reached >70 at a maximum).

I believe you increase yours - which may be the cause of paging, as all it will do is leave more processes running but waiting (and hence consuming memory).

[twol]

Luck! If you get only nodejs and qt building at the same time ( that is just 2 streams) you can hit 34 gb (no swapping - I have excess memory on my PC ) and all 16 cpus running

[ronand]

Even with 24GB RAM I've needed to use a swap file on my old i7 920 (8 threads). Currently using an equally old 4th gen i5 machine (4 threads) with 8GB RAM and 16GB swap and its building OK.

[birdman]

Luck! If you get only nodejs and qt building at the same time ( that is just 2 streams) you can hit 34 gb (no swapping - I have excess memory on my PC ) and all 16 cpus running

You could add one to the DEPENDS of the other, which will stop them being built at the same time.
Probably requires that you are building both, as I can't find a way to make that conditional on the other being set to build anyway.

[littlejim]

There are two parameters in your site.conf that influence how many threads you have running at a time.

I build on a system with only 4 logical CPUs, and they seemed to deafult to:

BB_NUMBER_THREADS = "4"
PARALLEL_MAKE = "-j 4"

for me. (both equal to the number of logical CPUs). A strategy that should be a good choice for building as fast as possible.

The first one controls how many bitbakes run at a time.
The second controls how many threads some of the various bit of software that bitbake uses can use.

So, for example, the above values mean up to 4 bitbakes can be running and they can each be using up to 4 threads.
This means that potentially there can be a lot more threads running than is needed to use all 4 logical CPUs, all using up RAM.

You can actually reduce the numbers and still be utilizing the full power of all your logical CPUs almost all of the time while greatly reducing the amount of RAM you'll need to ensure your build never crashes due to running out of RAM. It works best on systems with good fast I/O (an SSD).

If you have a large number of logical CPUs and are having trouble due to running out of RAM try experimenting with the values.
You're likely to find your builds really don't take much longer if you reduce the values a bit.
I think reducing the second parameter is likely to be the most useful, but you can try various combinations.

[birdman]

Luck! If you get only nodejs and qt building at the same time ( that is just 2 streams) you can hit 34 gb (no swapping - I have excess memory on my PC ) and all 16 cpus running

Perhaps not so lucky, really.

Just realized that my systems don't build qt (they do build nodejs).

[Huevos]

Can you give one good reason you are building nodejs?

[birdman]

Can you give one good reason you are building nodejs?

Because if I don't need it the standard Vix build shouldn't be building it for me - it should disable it.

[Huevos]

It is not in the "standard" ViX build, Release or Dev.

[bbbuk]

Hi,

I've decided to give building new openvix ago using this guide.

However, I'm getting stuck on step 1 (yes step 1 haha).

It is failing to find gcc-8 package. The error I get is:-

Package gcc-8 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'gcc-8' has no installation candidate

Removing gcc-8 from the list of packages to install, I can then install the rest of the packages without an issue.

I've stopped after this point as don't want to proceed further until I get gcc-8 installed.

I'm using Ubuntu 22.04.1

Anyone any ideas?

[Huevos]

Remember those instructions are for 20.04.

$ sudo apt update
$ sudo apt install build-essential

That should get you GCC.

Now check version:

$ gcc --version

I'm using 21.04 and looks like this:

$ gcc --version
gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[twol]

Hi,

I've decided to give building new openvix ago using this guide.

However, I'm getting stuck on step 1 (yes step 1 haha).

It is failing to find gcc-8 package. The error I get is:-

Package gcc-8 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'gcc-8' has no installation candidate

Removing gcc-8 from the list of packages to install, I can then install the rest of the packages without an issue.

I've stopped after this point as don't want to proceed further until I get gcc-8 installed.

I'm using Ubuntu 22.04.1

Anyone any ideas?

I shouldn‘t worry I have 22.04 and gcc is 11.2.0 …. And everything builds just fine

[birdman]

It is failing to find gcc-8 package.

Just install gcc. This will install the latest (11.2.0), which works fine.

[bbbuk]

Hi,

I've successfully followed this guide on building branch 5.1 and had no issues.

I created new folder and cloning the newer 5.2 branch but when I start the build off, I get the following error:-
branch52error.jpg

Could someone point me in correct direction on what/where I need to change to get passed this error?

PS: Once passed this error, should I expect anymore?

[Huevos]

Haven't seen that in any of my builds. That is an old variable, how has that got in the new env?

Try going in the machine folder (some thing like /home/openvix/6.3/builds/openvix/developer/vuultimo4k) and try the following:

. env.source
unset BB_ENV_EXTRAWHITE