From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 92e4521572f0a5a6411ce74a7a70b9b65dcebb26
Date: Fri, 22 Jan 2016 12:49:23 +0100 [thread overview]
Message-ID: <20160122114923.B7B1521287@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 92e4521572f0a5a6411ce74a7a70b9b65dcebb26 (commit)
from 20b27af8634b88fa400b1779415fc92888fbb1d8 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 92e4521572f0a5a6411ce74a7a70b9b65dcebb26
Author: Daniel Weismüller <daniel.weismueller(a)ipfire.org>
Date: Fri Jan 22 12:10:19 2016 +0100
cmake: Disable parallelism
Building cmake uses a high amount of memory (>2G) and
fails to build on my system. Using less processes reduces
memory usage and lets the build succeed.
Signed-off-by: Daniel Weismüller <daniel.weismueller(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/cmake | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
Difference in files:
diff --git a/lfs/cmake b/lfs/cmake
index e3d2119..a9ada50 100644
--- a/lfs/cmake
+++ b/lfs/cmake
@@ -32,9 +32,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
-ifeq "$(MACHINE)" "armv5tel"
- MAKETUNING = -j2
-endif
+MAKETUNING = -j2
###############################################################################
# Top-level Rules
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-01-22 11:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160122114923.B7B1521287@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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