From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-cluster/hpx/
Date: Fri, 24 Jul 2020 12:03:48 +0000 (UTC) [thread overview]
Message-ID: <1595592210.f29658991e1fd295f10bf26d7a1275eebc43befa.juippis@gentoo> (raw)
commit: f29658991e1fd295f10bf26d7a1275eebc43befa
Author: Kurt Kanzenbach <kurt <AT> kmk-computers <DOT> de>
AuthorDate: Sun Jul 12 14:18:09 2020 +0000
Commit: Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Fri Jul 24 12:03:30 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f2965899
sys-cluster/hpx: Fix memory requirement
Instead of guessing the number of make jobs, better use the corresponding eclass
to get it.
Closes: https://bugs.gentoo.org/732274
Package-Manager: Portage-2.3.99, Repoman-2.3.23
Signed-off-by: Kurt Kanzenbach <kurt <AT> kmk-computers.de>
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
sys-cluster/hpx/hpx-1.4.1.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sys-cluster/hpx/hpx-1.4.1.ebuild b/sys-cluster/hpx/hpx-1.4.1.ebuild
index 964325329bb..7206bca4082 100644
--- a/sys-cluster/hpx/hpx-1.4.1.ebuild
+++ b/sys-cluster/hpx/hpx-1.4.1.ebuild
@@ -12,7 +12,7 @@ else
SRC_URI="https://stellar.cct.lsu.edu/files/${PN}_${PV}.tar.gz"
KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux"
fi
-inherit cmake fortran-2 python-single-r1 check-reqs
+inherit cmake fortran-2 python-single-r1 check-reqs multiprocessing
DESCRIPTION="C++ runtime system for parallel and distributed applications"
HOMEPAGE="https://stellar.cct.lsu.edu/tag/hpx/"
@@ -65,7 +65,7 @@ hpx_memory_requirement() {
if [[ -z ${MAKEOPTS} ]] ; then
echo "2G"
else
- local jobs=`echo ${MAKEOPTS} | cut -d j -f 2`
+ local jobs=$(makeopts_jobs "${MAKEOPTS}" "$(get_nproc)")
echo "${jobs}G"
fi
}
next reply other threads:[~2020-07-24 12:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 12:03 Joonas Niilola [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-13 8:11 [gentoo-commits] repo/gentoo:master commit in: sys-cluster/hpx/ Joonas Niilola
2024-07-13 8:11 Joonas Niilola
2023-09-16 7:57 Joonas Niilola
2023-09-16 7:57 Joonas Niilola
2023-09-16 7:57 Joonas Niilola
2023-05-20 6:28 Sam James
2023-05-20 6:28 Sam James
2022-06-03 8:35 Florian Schmaus
2021-10-29 22:23 Sam James
2021-08-26 22:21 Sam James
2021-08-26 22:21 Sam James
2021-07-23 14:33 Joonas Niilola
2021-07-23 14:33 Joonas Niilola
2021-07-23 14:33 Joonas Niilola
2021-07-17 18:18 David Seifert
2020-10-31 9:47 Joonas Niilola
2020-07-24 12:03 Joonas Niilola
2020-03-28 14:21 Joonas Niilola
2020-03-28 14:21 Joonas Niilola
2020-03-28 14:21 Joonas Niilola
2020-03-28 14:21 Joonas Niilola
2020-03-25 11:17 Joonas Niilola
2020-02-10 13:26 Michał Górny
2020-01-01 13:28 Andreas Sturmlechner
2019-05-15 14:53 Andreas Sturmlechner
2019-05-15 14:53 Andreas Sturmlechner
2019-05-15 14:53 Andreas Sturmlechner
2019-05-15 14:53 Andreas Sturmlechner
2018-12-07 15:40 Christoph Junghans
2018-10-30 10:36 Christoph Junghans
2017-12-10 10:27 Pacho Ramos
2017-07-12 14:43 Pacho Ramos
2017-05-26 22:54 David Seifert
2017-05-12 8:07 Slawek Lis
2017-05-04 6:21 Slawek Lis
2016-07-22 20:12 Christoph Junghans
2016-07-22 20:12 Christoph Junghans
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=1595592210.f29658991e1fd295f10bf26d7a1275eebc43befa.juippis@gentoo \
--to=juippis@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