public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Thomas Deutschmann" <whissi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/openssl-compat/
Date: Sun, 15 Sep 2019 20:28:15 +0000 (UTC)	[thread overview]
Message-ID: <1568579282.3201627815cc92ff5f4396c288354fd3acfcd7c3.whissi@gentoo> (raw)

commit:     3201627815cc92ff5f4396c288354fd3acfcd7c3
Author:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 15 20:27:47 2019 +0000
Commit:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
CommitDate: Sun Sep 15 20:28:02 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=32016278

dev-libs/openssl-compat: limit parallel jobs

Bug: https://bugs.gentoo.org/694512
Package-Manager: Portage-2.3.76, Repoman-2.3.17
Signed-off-by: Thomas Deutschmann <whissi <AT> gentoo.org>

 dev-libs/openssl-compat/openssl-compat-1.0.2t.ebuild | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/dev-libs/openssl-compat/openssl-compat-1.0.2t.ebuild b/dev-libs/openssl-compat/openssl-compat-1.0.2t.ebuild
index 717d2d311a8..292f5d8fd0f 100644
--- a/dev-libs/openssl-compat/openssl-compat-1.0.2t.ebuild
+++ b/dev-libs/openssl-compat/openssl-compat-1.0.2t.ebuild
@@ -3,7 +3,7 @@
 
 EAPI="7"
 
-inherit flag-o-matic toolchain-funcs multilib multilib-minimal
+inherit flag-o-matic toolchain-funcs multiprocessing multilib multilib-minimal
 
 # openssl-1.0.2-patches-1.6 contain additional CVE patches
 # which got fixed with this release.
@@ -135,6 +135,13 @@ src_prepare() {
 	sed -i '/stty -icanon min 0 time 50; read waste/d' config || die
 	./config --test-sanity || die "I AM NOT SANE"
 
+	local make_jobs=$(makeopts_jobs)
+	if [[ ${make_jobs} -gt 6 ]] ; then
+		# bug 694512
+		einfo "Limiting parallel jobs to 6 ..."
+		export MAKEOPTS=-j6
+	fi
+
 	multilib_copy_sources
 }
 


             reply	other threads:[~2019-09-15 20:28 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-15 20:28 Thomas Deutschmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-25 15:24 [gentoo-commits] repo/gentoo:master commit in: dev-libs/openssl-compat/ Andreas K. Hüttel
2024-07-01 18:55 Mike Gilbert
2024-05-16 16:47 Arthur Zamarin
2024-04-04  1:07 Sam James
2023-09-09 20:24 Sam James
2023-06-22  3:08 Sam James
2023-06-22  2:49 Sam James
2023-06-14  5:22 Sam James
2023-05-30 16:01 Sam James
2023-05-13  3:23 Sam James
2022-12-15  6:16 Sam James
2022-11-15  8:46 Sam James
2022-06-11  5:12 Sam James
2021-07-21 12:56 Thomas Deutschmann
2020-05-19  9:49 Thomas Deutschmann
2020-05-19  9:49 Thomas Deutschmann
2020-05-08 23:28 Thomas Deutschmann
2020-01-01 21:25 Thomas Deutschmann
2020-01-01 21:25 Thomas Deutschmann
2019-12-21 20:31 Thomas Deutschmann
2019-11-25  0:42 Thomas Deutschmann
2019-11-02 14:56 Thomas Deutschmann
2019-10-22  7:45 Lars Wendler
2019-10-01 19:38 Thomas Deutschmann
2019-09-16  0:06 Thomas Deutschmann
2019-09-16  0:06 Thomas Deutschmann
2019-09-16  0:06 Thomas Deutschmann
2019-09-15 20:37 Thomas Deutschmann
2019-09-13 12:15 Mikle Kolyada
2019-09-13  0:00 Thomas Deutschmann
2019-09-12 13:57 Thomas Deutschmann
2019-08-23 18:10 Thomas Deutschmann

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=1568579282.3201627815cc92ff5f4396c288354fd3acfcd7c3.whissi@gentoo \
    --to=whissi@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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