From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 43d91dad5166c5c345fd936095373452155dfdbd
Date: Sun, 22 May 2016 18:38:27 +0100 [thread overview]
Message-ID: <20160522173828.289121078E81@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1498 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 43d91dad5166c5c345fd936095373452155dfdbd (commit)
from 3fffbe09e29089b7d849f0cd27ea902f2b864183 (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 43d91dad5166c5c345fd936095373452155dfdbd
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun May 22 10:56:57 2016 +0200
gcc: fix bootstrap with gcc-6
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/gcc | 2 ++
1 file changed, 2 insertions(+)
Difference in files:
diff --git a/lfs/gcc b/lfs/gcc
index 52d1dae..e0cd102 100644
--- a/lfs/gcc
+++ b/lfs/gcc
@@ -61,6 +61,8 @@ else
ifeq "$(PASS)" "1"
CFLAGS := $(patsubst -fstack-protector-strong,-fstack-protector-all,$(CFLAGS))
CXXFLAGS := $(patsubst -fstack-protector-strong,-fstack-protector-all,$(CXXFLAGS))
+ CXXFLAGS += -std=gnu++98
+
TARGET = $(DIR_INFO)/$(THISAPP)-tools1
EXTRA_CONFIG = \
--target=$(CROSSTARGET) \
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-05-22 17:38 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=20160522173828.289121078E81@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