From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 3.x development tree branch, master, updated. d72c8258c21fc52ee258ecb67ea0cd3a732032fa
Date: Fri, 13 Apr 2012 18:20:01 +0200 [thread overview]
Message-ID: <20120413162010.A87B5200D6@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1628 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 3.x development tree".
The branch, master has been updated
via d72c8258c21fc52ee258ecb67ea0cd3a732032fa (commit)
from 4cf37d600be0113d91ce012e4172d9b2451f2e34 (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 d72c8258c21fc52ee258ecb67ea0cd3a732032fa
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Apr 13 18:19:32 2012 +0200
gcc: Force the patch to properly enable the SSP.
-----------------------------------------------------------------------
Summary of changes:
gcc/gcc.nm | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/gcc/gcc.nm b/gcc/gcc.nm
index ed1b500..a87a9bf 100644
--- a/gcc/gcc.nm
+++ b/gcc/gcc.nm
@@ -8,7 +8,7 @@ build_cloog_ppl = 1
name = gcc
version = 4.6.3
-release = 3
+release = 4
maintainer = Michael Tremer <michael.tremer(a)ipfire.org>
groups = Development/Compilers
@@ -112,7 +112,8 @@ build
end
# CFLAGS for hardening.
- HARD_CFLAGS = -DEFAULT_PIE_SSP -DEFAULT_RELRO -DEFAULT_BIND_NOW
+ HARD_CFLAGS = -DEFAULT_PIE -DEFAULT_SSP -DEFAULT_PIE_SSP -DEFAULT_ESP_SPP \
+ -DENABLE_ESP_SSP -DEFAULT_RELRO -DEFAULT_BIND_NOW
prepare_cmds
mkdir -v %{DIR_SRC}/gcc-build
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-04-13 16: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=20120413162010.A87B5200D6@argus.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