From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e9fbc1cecf856ccc7f5f2b2c504aa4318e879a7d
Date: Wed, 11 Nov 2015 22:07:06 +0100 [thread overview]
Message-ID: <20151111210707.5D6DA21753@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1540 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 e9fbc1cecf856ccc7f5f2b2c504aa4318e879a7d (commit)
from dccbe309d2b568147c47a4d37c59b5686a7babbe (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 e9fbc1cecf856ccc7f5f2b2c504aa4318e879a7d
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Nov 11 22:05:15 2015 +0100
boost: build also on x86 with -j2
boost need to much memory if it was build with more
than 2 parallel processes.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/boost | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
Difference in files:
diff --git a/lfs/boost b/lfs/boost
index b9b5015..12c0a5b 100644
--- a/lfs/boost
+++ b/lfs/boost
@@ -48,9 +48,7 @@ CONFIGURE_OPTIONS = \
debug-symbols=off \
pch=off
-ifeq "$(MACHINE)" "armv5tel"
- MAKETUNING = -j2
-endif
+MAKETUNING = -j2
###############################################################################
# Top-level Rules
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-11-11 21:07 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=20151111210707.5D6DA21753@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