Re: [PATCH 0/1] Parallelized build for several packages

[Wolfgang Apolinarski <wolfgang.apolinarski@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]

Hi Arne,

of course I did delete the ccache between my multiple builds to verify the commit. To play it safe, I hard reset using git, checked that all folders (build, ccache, etc.) are gone and restarted the build after gettoolchain and downloadsrc.

Sorry, I did not know that there are still a lot of machines with low ram that we are using to build ipfire. My hope was that these machines have disappeared over the last years.
Additionally, I do not have the ability to test all ipfire arches, as mentioned, the patch needs testing by others.

I also thought of adding a manual parameter for developers that somehow manually sets the parameters for parallel build, but since the MAKETUNING parameter already exists and is used with other packages this would just somehow mess everything up.

For my builds, I can just manually apply the patch to speed up the full build. My thought was that sharing the patch would make sense for others.

> -----Ursprüngliche Nachricht-----
> Von: Arne Fitzenreiter <Arne.Fitzenreiter(a)ipfire.org>
> Gesendet: Donnerstag, 21. Februar 2019 09:44
> An: Wolfgang Apolinarski <wolfgang.apolinarski(a)ipfire.org>
> Cc: development(a)lists.ipfire.org
> Betreff: Re: [PATCH 0/1] Parallelized build for several packages
> 
> On the most of this packages (eg. boot and cmake) i have disabled
> parallel build because it fails on machines with low ram (less than 2GB)
> or on arm.
> So such changes need tested on an 1GB machine, on all architectures and
> build two times after deleting ccache. Because the build need much lower
> resources if it has the file already prebuilt in cache.