From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-dev] [PATCH 4/4] sys-apps/systemd: Use eninja from ninja-utils
Date: Sun, 30 Apr 2017 22:28:30 +0200 [thread overview]
Message-ID: <20170430202830.12974-4-mgorny@gentoo.org> (raw)
In-Reply-To: <20170430202830.12974-1-mgorny@gentoo.org>
---
sys-apps/systemd/systemd-9999.ebuild | 11 +----------
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/sys-apps/systemd/systemd-9999.ebuild b/sys-apps/systemd/systemd-9999.ebuild
index 7ff69d75cc9a..b4e1f943a599 100644
--- a/sys-apps/systemd/systemd-9999.ebuild
+++ b/sys-apps/systemd/systemd-9999.ebuild
@@ -13,7 +13,7 @@ fi
PYTHON_COMPAT=( python{3_4,3_5,3_6} )
-inherit bash-completion-r1 linux-info multilib-minimal multiprocessing pam python-any-r1 systemd toolchain-funcs udev user
+inherit bash-completion-r1 linux-info multilib-minimal ninja-utils pam python-any-r1 systemd toolchain-funcs udev user
DESCRIPTION="System and service manager for Linux"
HOMEPAGE="https://www.freedesktop.org/wiki/Software/systemd"
@@ -271,15 +271,6 @@ multilib_src_configure() {
"$@" || die
}
-eninja() {
- if [[ -z ${NINJAOPTS+set} ]]; then
- NINJAOPTS="-j $(makeopts_jobs) -l $(makeopts_loadavg "${MAKEOPTS}" 0)"
- fi
- set -- ninja -v ${NINJAOPTS} "$@"
- echo "$@"
- "$@" || die
-}
-
multilib_src_compile() {
eninja
}
--
2.13.0.rc1
next prev parent reply other threads:[~2017-04-30 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 20:28 [gentoo-dev] [PATCH 1/4] ninja-utils.eclass: Add a new eclass to handle calling ninja Michał Górny
2017-04-30 20:28 ` [gentoo-dev] [PATCH 2/4] cmake-utils.eclass: Use eninja from ninja-utils Michał Górny
2017-04-30 20:28 ` [gentoo-dev] [PATCH 3/4] www-client/chromium: " Michał Górny
2017-05-01 11:17 ` Paweł Hajdan, Jr.
2017-04-30 20:28 ` Michał Górny [this message]
2017-05-16 17:12 ` [gentoo-dev] [PATCH 1/4] ninja-utils.eclass: Add a new eclass to handle calling ninja Michał Górny
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=20170430202830.12974-4-mgorny@gentoo.org \
--to=mgorny@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