public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-python@lists.gentoo.org
Cc: python@gentoo.org, "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-python] [PATCH distutils-r1 3/4] multiprocessing: use the expanded call form.
Date: Thu,  6 Dec 2012 11:54:56 +0100	[thread overview]
Message-ID: <1354791297-19239-4-git-send-email-mgorny@gentoo.org> (raw)
In-Reply-To: <1354791297-19239-1-git-send-email-mgorny@gentoo.org>

The short one doesn't want to work with pipes, for some reason.
---
 gx86/eclass/distutils-r1.eclass | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/gx86/eclass/distutils-r1.eclass b/gx86/eclass/distutils-r1.eclass
index 1006813..8ba2aa8 100644
--- a/gx86/eclass/distutils-r1.eclass
+++ b/gx86/eclass/distutils-r1.eclass
@@ -382,7 +382,11 @@ distutils-r1_run_phase() {
 	if [[ ${DISTUTILS_NO_PARALLEL_BUILD} ]]; then
 		"${@}"
 	else
-		multijob_child_init --post "${@}"
+		(
+			multijob_child_init
+			"${@}"
+		) &
+		multijob_post_fork
 	fi
 
 	if [[ ${DISTUTILS_IN_SOURCE_BUILD} ]]; then
-- 
1.8.0



  parent reply	other threads:[~2012-12-06 10:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 10:54 [gentoo-python] [distutils-r1] Improvements to parallel builds Michał Górny
2012-12-06 10:54 ` [gentoo-python] [PATCH distutils-r1 1/4] Don't rely on phase function return code Michał Górny
2012-12-06 10:54 ` [gentoo-python] [PATCH distutils-r1 2/4] Use post-fork mode to avoid early output Michał Górny
2012-12-06 10:54 ` Michał Górny [this message]
2012-12-06 10:54 ` [gentoo-python] [PATCH distutils-r1 4/4] Create split logs when doing parallel builds Michał Górny
2012-12-06 17:28 ` [gentoo-python] Re: [distutils-r1] Improvements to " Mike Gilbert
2012-12-06 17:40   ` 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=1354791297-19239-4-git-send-email-mgorny@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-python@lists.gentoo.org \
    --cc=python@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