From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 512111959126a5484b575a983b20e07b24f0968d
Date: Wed, 06 Dec 2023 07:21:30 +0000 [thread overview]
Message-ID: <4SlTNc3865z2xf8@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2487 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 512111959126a5484b575a983b20e07b24f0968d (commit)
via ea381f64a8426ad89ef7d49c80d5cbd9ada8147c (commit)
from 43d72238cb760e409d9912a35eb28406eee539de (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 512111959126a5484b575a983b20e07b24f0968d
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Dec 6 08:18:42 2023 +0100
gcc: fix toolchain crossbuild
gcc doesn't support mbranch-predict=standard on x86_64
so this is removed in toolchain pass1
commit ea381f64a8426ad89ef7d49c80d5cbd9ada8147c
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Dec 6 08:16:33 2023 +0100
binutils: fix toolchain crossbuild
gcc on x86_64 doesn't support mbrach-predict=standard so this has removed
for toolchain pass1
-----------------------------------------------------------------------
Summary of changes:
lfs/binutils | 2 ++
lfs/gcc | 1 +
2 files changed, 3 insertions(+)
Difference in files:
diff --git a/lfs/binutils b/lfs/binutils
index 2b5c65592..b4b3cd921 100644
--- a/lfs/binutils
+++ b/lfs/binutils
@@ -51,6 +51,8 @@ ifeq "$(PASS)" "1"
CFLAGS := $(patsubst -mfloat-abi=%,,$(CFLAGS))
CFLAGS := $(patsubst -mindirect-branch=%,,$(CFLAGS))
CFLAGS := $(patsubst -mfunction-return=%,,$(CFLAGS))
+ CFLAGS := $(patsubst -mbranch-protection=%,,$(CFLAGS))
+ CXXFLAGS := $(patsubst -mbranch-protection=%,,$(CXXFLAGS))
CFLAGS := $(patsubst -fstack-clash-protection,,$(CFLAGS))
CFLAGS := $(patsubst -fcf-protection,,$(CFLAGS))
diff --git a/lfs/gcc b/lfs/gcc
index c979aa199..5183903c7 100644
--- a/lfs/gcc
+++ b/lfs/gcc
@@ -43,6 +43,7 @@ CFLAGS := $(patsubst -mfloat-abi=%,,$(CFLAGS))
CFLAGS := $(filter-out -fexceptions,$(CFLAGS))
CFLAGS := $(patsubst -mindirect-branch=%,,$(CFLAGS))
+CFLAGS := $(patsubst -mbranch-protection=%,,$(CFLAGS))
CFLAGS := $(patsubst -mfunction-return=%,,$(CFLAGS))
CFLAGS := $(patsubst -fstack-clash-protection,,$(CFLAGS))
CFLAGS := $(patsubst -fcf-protection,,$(CFLAGS))
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2023-12-06 7:21 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=4SlTNc3865z2xf8@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