From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] packages/exim: enable parallel make
Date: Wed, 06 May 2020 09:39:40 +0200 [thread overview]
Message-ID: <87o8r1bjgj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <26ba2f56-3ac7-3364-848c-4d0cd3a8c9a3@lucaceresoli.net> (Luca Ceresoli's message of "Wed, 6 May 2020 09:09:39 +0200")
>>>>> "Luca" == Luca Ceresoli <luca@lucaceresoli.net> writes:
> Hi Peter,
> On 06/05/20 08:00, Peter Korsgaard wrote:
>>>>>>> "Luca" == Luca Ceresoli <luca@lucaceresoli.net> writes:
>>
>> > Parallel make used to be broken in exim, as reported in its docs. Now that
>> > line has disappeared from the docs, and parallel make is actually working.
>>
>> > Tested with 'make exim-dirclean ; time make BR2_JLEVEL=999 exim': builds
>> > still succeed and the build time decreases from 34 to 11 seconds on my
>> > host.
>>
>> > Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
>> > Cc: Bernd Kuhls <bernd.kuhls@t-online.de>
>>
>> Committed to 2020.02.x, thanks.
> Does this patch really belong to a stable branch?
I agree that it is a gray zone. Given that there weren't any followup
fixups on master since then (or so I thought, it turned out my tree was
not uptodate) I found it "safe".
> If it does, then you should also apply [0] or we'll start seeing
> parallel build failures on 2020.02.x too.
> [0]
> https://git.busybox.net/buildroot/commit/?id=8c75f95e0a3d2600015be5564ee9fe9393d95ebc
I'll do so later today. Yann also pointed that out to me.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2020-05-06 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 16:36 [Buildroot] [PATCH] packages/exim: enable parallel make Luca Ceresoli
2020-04-20 19:03 ` Bernd Kuhls
2020-04-20 21:08 ` Yann E. MORIN
2020-05-06 6:00 ` Peter Korsgaard
2020-05-06 7:09 ` Luca Ceresoli
2020-05-06 7:39 ` Peter Korsgaard [this message]
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=87o8r1bjgj.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.