From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 44bfc406407fcba783b532ce5e5bcd91092e08d0
Date: Mon, 17 Aug 2020 10:06:06 +0000 [thread overview]
Message-ID: <4BVV726y7Wz2xc7@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1490 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 44bfc406407fcba783b532ce5e5bcd91092e08d0 (commit)
from 815ca15dc4e7e3d20a5fd7006395c9b1664bb04c (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 44bfc406407fcba783b532ce5e5bcd91092e08d0
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Aug 17 10:05:40 2020 +0000
glibc: aarch64: Ignore uninitialised variables in the stage2 build, too
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/glibc | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/glibc b/lfs/glibc
index abb8b54bb..802c372a9 100644
--- a/lfs/glibc
+++ b/lfs/glibc
@@ -49,8 +49,10 @@ else
--with-headers=$(TOOLS_DIR)/include \
libc_cv_forced_unwind=yes \
libc_cv_c_cleanup=yes
+endif
- CFLAGS += -Wno-error=maybe-uninitialized
+ifeq "$(BUILD_ARCH)" "aarch64"
+ CFLAGS += -Wno-error=maybe-uninitialized
endif
# Disable hardware FP for armv5tel
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-08-17 10:06 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=4BVV726y7Wz2xc7@people01.haj.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