public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. b5aca95b9401ba610fad2f8bcb9b4862f98a4969
Date: Tue, 28 Nov 2017 06:04:01 +0000	[thread overview]
Message-ID: <20171128060401.8A89A1081BCF@git01.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2023 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  b5aca95b9401ba610fad2f8bcb9b4862f98a4969 (commit)
      from  0476a6570d5fba5935d0ef4d5d0af9c483c819c3 (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 b5aca95b9401ba610fad2f8bcb9b4862f98a4969
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Tue Nov 28 07:01:33 2017 +0100

    boost: disable parallel build
    
    this need more than 1GB ram on arm
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 lfs/boost | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

Difference in files:
diff --git a/lfs/boost b/lfs/boost
index 533cb24..29c7bad 100644
--- a/lfs/boost
+++ b/lfs/boost
@@ -55,8 +55,6 @@ CONFIGURE_OPTIONS = \
 	cflags="$(CFLAGS)" \
 	cxxflags="$(CXXFLAGS)"
 
-MAKETUNING = -j2
-
 ###############################################################################
 # Top-level Rules
 ###############################################################################
@@ -97,8 +95,8 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
 	@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE)
 
 	cd $(DIR_APP) && ./bootstrap.sh --with-toolset=gcc
-	cd $(DIR_APP) && ./b2 -d+2 -q $(MAKETUNING) $(CONFIGURE_OPTIONS) stage
-	cd $(DIR_APP) && ./b2 $(MAKETUNING) $(CONFIGURE_OPTIONS) install
+	cd $(DIR_APP) && ./b2 -d+2 -q $(CONFIGURE_OPTIONS) stage
+	cd $(DIR_APP) && ./b2 $(CONFIGURE_OPTIONS) install
 
 	@rm -rf $(DIR_APP)
 	@$(POSTBUILD)


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2017-11-28  6:04 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=20171128060401.8A89A1081BCF@git01.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