From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 955ab2f5c3a06b2c29ee9b992f80d20759fc4fc8
Date: Tue, 06 Jul 2021 04:20:31 +0000 [thread overview]
Message-ID: <4GJq9C41Fkz2xrB@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1570 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 955ab2f5c3a06b2c29ee9b992f80d20759fc4fc8 (commit)
from ede29dd5564bf370735045135289f764bbac8150 (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 955ab2f5c3a06b2c29ee9b992f80d20759fc4fc8
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Jul 6 06:18:09 2021 +0200
glibc: fix for older i?86 cpu's
with such cpu the libc fails with CPU ISA level is lower than required. So this disable
ISA support.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/glibc | 4 ++++
1 file changed, 4 insertions(+)
Difference in files:
diff --git a/lfs/glibc b/lfs/glibc
index 8bbae1746..aa7948aed 100644
--- a/lfs/glibc
+++ b/lfs/glibc
@@ -55,6 +55,10 @@ ifeq "$(BUILD_ARCH)" "aarch64"
CFLAGS += -Wno-error=maybe-uninitialized
endif
+ifeq "$(BUILD_ARCH)" "i586"
+ EXTRA_CONFIG += libc_cv_include_x86_isa_level=no
+endif
+
# Add some general configuration flags
EXTRA_CONFIG += \
--disable-profile \
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2021-07-06 4:20 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=4GJq9C41Fkz2xrB@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