From: "H. Peter Anvin" <hpa@zytor.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: [PATCH] Parallelize building rpm
Date: Mon, 26 Sep 2005 19:48:39 -0700 [thread overview]
Message-ID: <4338B307.7010405@zytor.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 208 bytes --]
Allow parallelization of rpm build by adding %{_smp_mflags} to the
specfile. The absence of this macro in a specfile means a make should
not be parallelized.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
[-- Attachment #2: git-makej-patch --]
[-- Type: text/plain, Size: 1284 bytes --]
---
commit b8d5dfede58c6e787b06edf9a179b54876ef04db
tree fb5f6eabbc1cf9c57f0d6c2f52db334faa704269
parent 4ae95682694a1cd05ee2029fe241ad90d43c8c0e
author H. Peter Anvin <hpa@hera.kernel.org> Mon, 26 Sep 2005 19:43:24 -0700
committer H. Peter Anvin <hpa@hera.kernel.org> Mon, 26 Sep 2005 19:43:24 -0700
git-core.spec.in | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/git-core.spec.in b/git-core.spec.in
--- a/git-core.spec.in
+++ b/git-core.spec.in
@@ -23,12 +23,12 @@ elsewhere for tools for ordinary humans
%setup -q
%build
-make COPTS="$RPM_OPT_FLAGS" WITH_OWN_SUBPROCESS_PY=YesPlease \
+make %{_smp_mflags} COPTS="$RPM_OPT_FLAGS" WITH_OWN_SUBPROCESS_PY=YesPlease \
prefix=%{_prefix} all %{!?_without_docs: doc}
%install
rm -rf $RPM_BUILD_ROOT
-make DESTDIR=$RPM_BUILD_ROOT WITH_OWN_SUBPROCESS_PY=YesPlease \
+make %{_smp_mflags} DESTDIR=$RPM_BUILD_ROOT WITH_OWN_SUBPROCESS_PY=YesPlease \
prefix=%{_prefix} mandir=%{_mandir} \
install %{!?_without_docs: install-doc}
@@ -45,6 +45,9 @@ rm -rf $RPM_BUILD_ROOT
%{!?_without_docs: %{_mandir}/man7/*.7*}
%changelog
+* Mon Sep 26 2005 H. Peter Anvin <hpa@zytor.com>
+- add %{_smp_mflags}
+
* Fri Sep 16 2005 Chris Wright <chrisw@osdl.org> 0.99.6-1
- update to 0.99.6
next reply other threads:[~2005-09-27 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 2:48 H. Peter Anvin [this message]
2005-09-27 4:21 ` [PATCH] Parallelize building rpm Junio C Hamano
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=4338B307.7010405@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).