From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e6aa297eb3b9b1f4d8047091a9cce5f5aa225ae8
Date: Mon, 02 Jul 2018 18:52:17 +0100 [thread overview]
Message-ID: <20180702175218.1F6371081BCF@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1518 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 e6aa297eb3b9b1f4d8047091a9cce5f5aa225ae8 (commit)
from 4d2c384543fdd50b2471a5442f7f91361f6a74ff (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 e6aa297eb3b9b1f4d8047091a9cce5f5aa225ae8
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Jul 2 18:48:50 2018 +0100
nss-myhostname: FTBFS on aarch64
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/nss-myhostname | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/lfs/nss-myhostname b/lfs/nss-myhostname
index 9274e7588..36b071fb2 100644
--- a/lfs/nss-myhostname
+++ b/lfs/nss-myhostname
@@ -70,6 +70,7 @@ $(subst %,%_MD5,$(objects)) :
$(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
@$(PREBUILD)
@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE)
+ $(UPDATE_AUTOMAKE)
cd $(DIR_APP) && ./configure --prefix=/usr --libdir=/lib
cd $(DIR_APP) && make $(MAKETUNING)
cd $(DIR_APP) && make install
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-07-02 17:52 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=20180702175218.1F6371081BCF@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