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. 979f8700b26fc442f021f8a6fe891e05b76aabe0
Date: Sun, 10 Dec 2017 07:19:51 +0000	[thread overview]
Message-ID: <20171210071951.911091081DE6@git01.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3367 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  979f8700b26fc442f021f8a6fe891e05b76aabe0 (commit)
       via  ce9264a1c1ce3d6812b59204a06041a69bd24e95 (commit)
      from  51d1e9ce4d7f2305bc7cc868a48810a6ef268f4d (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 979f8700b26fc442f021f8a6fe891e05b76aabe0
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sun Dec 10 08:18:06 2017 +0100

    make.sh limit build to 23 parallel threads.
    
    perl will not work with more parallel build processes.
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

commit ce9264a1c1ce3d6812b59204a06041a69bd24e95
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sun Dec 10 07:59:43 2017 +0100

    strip: use toolchain binary inside of chroot to strip
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

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

Summary of changes:
 lfs/strip |  3 ++-
 make.sh   | 11 +++++++++--
 2 files changed, 11 insertions(+), 3 deletions(-)

Difference in files:
diff --git a/lfs/strip b/lfs/strip
index 084082e7b..b22cfb9a3 100644
--- a/lfs/strip
+++ b/lfs/strip
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007  Michael Tremer & Christian Schmidt                      #
+# Copyright (C) 2007-2017  IPFire Team  <info(a)ipfire.org>                     #
 #                                                                             #
 # This program is free software: you can redistribute it and/or modify        #
 # it under the terms of the GNU General Public License as published by        #
@@ -36,6 +36,7 @@ ifeq "$(TOOLCHAIN)" "1"
 else
 	SHELL = $(TOOLS_DIR)/bin/bash
 	STRIP = $(TOOLS_DIR)/bin/strip
+	ROOT = /
 endif
 
 ###############################################################################
diff --git a/make.sh b/make.sh
index bb80f3c05..16d6eddff 100755
--- a/make.sh
+++ b/make.sh
@@ -217,6 +217,12 @@ configure_build() {
 			parallelism=${cpu_max}
 		fi
 
+		# limit to -j23 because perl will not build
+		# more
+		if [ ${parallelism} -gt 23 ]; then
+			parallelism=23
+		fi
+
 		MAKETUNING="-j${parallelism}"
 	fi
 }
@@ -627,7 +633,7 @@ lfsmake2() {
 	local PS1='\u:\w$ '
 
 	enterchroot \
-		bash -x -c "cd /usr/src/lfs && \
+		${EXTRA_PATH}bash -x -c "cd /usr/src/lfs && \
 			MAKETUNING=${MAKETUNING} \
 			make -f $* \
 			LFS_BASEDIR=/usr/src install" \
@@ -1526,7 +1532,8 @@ buildinstaller() {
   export LOGFILE
   lfsmake2 memtest
   lfsmake2 installer
-  lfsmake1 strip
+  # use toolchain bash for chroot to strip
+  EXTRA_PATH=${TOOLS_DIR}/bin/ lfsmake2 strip
 }
 
 buildpackages() {


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

                 reply	other threads:[~2017-12-10  7:19 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=20171210071951.911091081DE6@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