From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. fdc0944aa7125a536292e5d21973deda66ddab0f
Date: Thu, 01 Jun 2017 10:16:40 +0100 [thread overview]
Message-ID: <20170601091640.8E02C10853C3@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1630 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 fdc0944aa7125a536292e5d21973deda66ddab0f (commit)
from 33848e1d24e1667bb75f081f61c92bef511a91af (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 fdc0944aa7125a536292e5d21973deda66ddab0f
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Jun 1 10:13:31 2017 +0100
make.sh: Fix MAKETUNING
This variable was not passed any more after the toolchain stage
which caused builds to be very slow.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
tools/make-functions | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/tools/make-functions b/tools/make-functions
index 62f1664..8e40163 100644
--- a/tools/make-functions
+++ b/tools/make-functions
@@ -645,7 +645,9 @@ lfsmake2() {
local PS1='\u:\w$ '
enterchroot \
- bash -x -c "cd /usr/src/lfs && make -f $* LFS_BASEDIR=/usr/src install" \
+ bash -x -c "cd /usr/src/lfs && make -f $* \
+ MAKETUNING=${MAKETUNING} \
+ LFS_BASEDIR=/usr/src install" \
>> ${LOGFILE} 2>&1
local COMPILE_SUCCESS=$?
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-06-01 9:16 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=20170601091640.8E02C10853C3@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