From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 357b8c14111373a8d4e02b9e9b9506e6d83c40be
Date: Wed, 07 Jun 2017 17:56:08 +0100 [thread overview]
Message-ID: <20170607165608.CAB571078E83@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1398 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 357b8c14111373a8d4e02b9e9b9506e6d83c40be (commit)
from b7ab17ad83877436f13215cc850e993ade0cb846 (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 357b8c14111373a8d4e02b9e9b9506e6d83c40be
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Jun 7 09:12:26 2017 +0100
bash: Fix toolchain build again
I am too stupid to get this right
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/bash | 2 ++
1 file changed, 2 insertions(+)
Difference in files:
diff --git a/lfs/bash b/lfs/bash
index 04e6c50..e98b6fd 100644
--- a/lfs/bash
+++ b/lfs/bash
@@ -101,6 +101,8 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
ifeq "$(TOOLCHAIN)" "1"
ln -svf bash /tools/bin/sh
+
+ mkdir -pv $(ROOT)/bin
ln -svf ../tools/bin/bash $(ROOT)/bin/sh
else
ln -svf bash /bin/sh
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-06-07 16:56 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=20170607165608.CAB571078E83@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