From: Wolfgang Apolinarski <wolfgang.apolinarski@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 0/1] Parallelized build for several packages
Date: Wed, 20 Feb 2019 20:18:05 +0100 [thread overview]
Message-ID: <20190220191806.2917-1-wolfgang.apolinarski@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]
With this patch, I tried to optimize the build (because it really takes
a long time if I compile from scratch for testing).
Nowadays, most packages are already optimizing for parallel build. I was
testing the build on an 8 core system (i.e., MAKETUNING is -j9).
I also found out something else, the collectd package build crashes when
libstatgrab is already built:
https://github.com/collectd/collectd/issues/445
Someone else already noticed this on the list, without discovering the
cause. An upgrade of collectd would be required to solve this problem.
Since I am not sure for what collectd is actually used (and a major
upgrade would be required), I did not perform this.
Speed-up:
Package | Before | After
boost | 1:20:41 | 13:39
cyrus-imapd | 3:50 | 0:48
dnsdist | 5:23 | 1:18
gcc | 46:15 | 11:29
gettext | 9:55 | 4:56
gutenprint | 3:14 | 1:22
ipfire-netboot | 9:33 | 2:07
krb5 | 5:28 | 1:27
lcd4linux | 1:04 | 0:27
netsnmpd | 8:00 | 3:33
nut | 1:59 | 0:21
openssl | 7:57 | 2:37
rrdtool | 1:31 | 0:32
samba | 5:03 | 0:55
slang | 1:04 | 0:19
snort | 5:11 | 0:56
xfsprogs | 5:41 | 1:46
I also marked packages that (in their current version) crash when being
built in parallel. I performed multiple builds (and tested the ISO
image), so I hope that this patch is reliable for everyone.
Nevertheless, please test the patch on different build environments
before applying it.
Wolfgang Apolinarski (1):
Parallelized build for several packages
lfs/boost | 2 +-
lfs/collectd | 2 +-
lfs/cyrus-imapd | 2 +-
lfs/dhcp | 2 +-
lfs/dnsdist | 2 +-
lfs/gcc | 4 ++--
lfs/gettext | 8 ++++----
lfs/groff | 2 +-
lfs/gutenprint | 2 +-
lfs/ipfire-netboot | 4 ++--
lfs/krb5 | 2 +-
lfs/lcd4linux | 2 +-
lfs/netpbm | 2 +-
lfs/netsnmpd | 2 +-
lfs/nut | 2 +-
lfs/openssl | 2 +-
lfs/rrdtool | 2 +-
lfs/samba | 4 ++--
lfs/slang | 2 +-
lfs/snort | 2 +-
lfs/xfsprogs | 2 +-
21 files changed, 27 insertions(+), 27 deletions(-)
--
2.19.2
next reply other threads:[~2019-02-20 19:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 19:18 Wolfgang Apolinarski [this message]
2019-02-20 19:18 ` [PATCH 1/1] " Wolfgang Apolinarski
2019-02-21 8:44 ` [PATCH 0/1] " Arne Fitzenreiter
2019-02-21 17:28 Wolfgang Apolinarski
2019-03-06 16:36 ` Michael Tremer
2019-03-08 10:17 ` Michael Tremer
2019-03-08 15:58 ` Matthias Fischer
2019-03-08 18:16 ` Matthias Fischer
2019-03-09 20:24 Wolfgang Apolinarski
2019-03-09 20:36 ` Matthias Fischer
2019-03-10 18:24 ` Michael Tremer
2019-03-10 19:17 ` ummeegge
2019-03-11 9:37 ` Michael Tremer
2019-03-11 17:07 ` ummeegge
2019-03-11 17:50 Wolfgang Apolinarski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190220191806.2917-1-wolfgang.apolinarski@ipfire.org \
--to=wolfgang.apolinarski@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox