From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/openssl: Enable parallel build
Date: Sat, 7 Mar 2015 21:31:36 -0500 [thread overview]
Message-ID: <20150308023136.GS12857@vapier> (raw)
In-Reply-To: <20141118225525.6e8b4e02@free-electrons.com>
On 18 Nov 2014 22:55, Thomas Petazzoni wrote:
> Unfortunately, this patch is a fairly large patch, which is more a
> feature patch than a real fix. Could we instead get it merged upstream?
i've tried before and only got some of it in. i could try again since upstream
openssl has changed a bit.
> I discussed this with Yann, and I believe Peter will agree that it's a
> feature patch that we shouldn't take in Buildroot. The solutions are
> either to take this patch upstream, or in Buildroot build in parallel
> and then fallback to serial build if the parallel build has failed.
> Something along the lines of:
>
> $(MAKE) -C $(@D) || $(MAKE1) -C $(@D)
unfortunately, that is not safe. it might end up with incomplete static
archives. at least, that was some of the errors we saw in the past that
made me investigate making openssl parallel safe.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150307/c15d7112/attachment.asc>
next prev parent reply other threads:[~2015-03-08 2:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 14:00 [Buildroot] [PATCH 1/2] package/openssl: Enable parallel build Bernd Kuhls
2014-11-16 14:00 ` [Buildroot] [PATCH 2/2] package/openssl: rename patches to the new convention Bernd Kuhls
2014-11-18 22:38 ` Thomas Petazzoni
2014-11-18 21:55 ` [Buildroot] [PATCH 1/2] package/openssl: Enable parallel build Thomas Petazzoni
2014-11-18 22:01 ` Peter Korsgaard
2015-03-08 2:31 ` Mike Frysinger [this message]
2015-03-08 7:13 ` Thomas Petazzoni
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=20150308023136.GS12857@vapier \
--to=vapier@gentoo.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox