From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e2d4f687dcd1e5e240f278d5c99d27fe75cd76bf
Date: Sat, 26 Jul 2014 20:43:42 +0200 [thread overview]
Message-ID: <20140726184342.6A2662133B@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1454 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 e2d4f687dcd1e5e240f278d5c99d27fe75cd76bf (commit)
from c226543b96ca82aee815a433ed026cf3d3cbd3f8 (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 e2d4f687dcd1e5e240f278d5c99d27fe75cd76bf
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Jul 26 18:42:37 2014 +0000
boost: Don't run more than two build processes at once
-----------------------------------------------------------------------
Summary of changes:
lfs/boost | 4 ++++
1 file changed, 4 insertions(+)
Difference in files:
diff --git a/lfs/boost b/lfs/boost
index 4057d87..b9b5015 100644
--- a/lfs/boost
+++ b/lfs/boost
@@ -48,6 +48,10 @@ CONFIGURE_OPTIONS = \
debug-symbols=off \
pch=off
+ifeq "$(MACHINE)" "armv5tel"
+ MAKETUNING = -j2
+endif
+
###############################################################################
# Top-level Rules
###############################################################################
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-07-26 18:43 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=20140726184342.6A2662133B@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