From: "Magnus Granberg" <zorry@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-dev:master commit in: sys-devel/gcc/
Date: Fri, 6 Apr 2012 19:39:55 +0000 (UTC) [thread overview]
Message-ID: <1333741177.c104a5cc32ffdd07592093b1545adc55980e8e62.zorry@gentoo> (raw)
commit: c104a5cc32ffdd07592093b1545adc55980e8e62
Author: Magnus Granberg <zorry <AT> gentoo <DOT> org>
AuthorDate: Fri Apr 6 19:39:37 2012 +0000
Commit: Magnus Granberg <zorry <AT> gentoo <DOT> org>
CommitDate: Fri Apr 6 19:39:37 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-dev.git;a=commit;h=c104a5cc
New version of gcc
---
sys-devel/gcc/gcc-4.6.3.ebuild | 2 +-
...4.7.0_alpha20120121.ebuild => gcc-4.7.0.ebuild} | 9 +++++----
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/sys-devel/gcc/gcc-4.6.3.ebuild b/sys-devel/gcc/gcc-4.6.3.ebuild
index 54bb333..d569e11 100644
--- a/sys-devel/gcc/gcc-4.6.3.ebuild
+++ b/sys-devel/gcc/gcc-4.6.3.ebuild
@@ -2,7 +2,7 @@
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/sys-devel/gcc/gcc-4.6.2.ebuild,v 1.9 2012/03/15 20:21:44 vapier Exp $
-PATCH_VER="1.0"
+PATCH_VER="1.1"
UCLIBC_VER="1.0"
# Hardened gcc 4 stuff
diff --git a/sys-devel/gcc/gcc-4.7.0_alpha20120121.ebuild b/sys-devel/gcc/gcc-4.7.0.ebuild
similarity index 92%
rename from sys-devel/gcc/gcc-4.7.0_alpha20120121.ebuild
rename to sys-devel/gcc/gcc-4.7.0.ebuild
index 33cfbc6..00d3b77 100644
--- a/sys-devel/gcc/gcc-4.7.0_alpha20120121.ebuild
+++ b/sys-devel/gcc/gcc-4.7.0.ebuild
@@ -2,11 +2,11 @@
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/sys-devel/gcc/gcc-4.7.0.ebuild,v 1.0 2012/01/17 19:02:25 zorry Exp $
-PATCH_VER="1.0"
-#UCLIBC_VER="1.0"
+PATCH_VER="1.1"
+UCLIBC_VER="1.0"
# Hardened gcc 4 stuff
-PIE_VER="0.5.2"
+PIE_VER="0.5.3"
SPECS_VER="0.2.0"
SPECS_GCC_VER="4.4.3"
# arch/libc configurations known to be stable with {PIE,SSP}-by-default
@@ -14,7 +14,8 @@ PIE_GLIBC_STABLE="x86 amd64 ppc ppc64 arm ia64"
PIE_UCLIBC_STABLE="x86 arm amd64 ppc ppc64"
SSP_STABLE="amd64 x86 ppc ppc64 arm"
# uclibc need tls and nptl support for SSP support
-SSP_UCLIBC_STABLE=""
+# uclibc 0.9.32 or newer.
+SSP_UCLIBC_STABLE="x86 amd64 ppc pcc64"
#end Hardened stuff
inherit toolchain
next reply other threads:[~2012-04-06 19:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 19:39 Magnus Granberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-24 14:32 [gentoo-commits] proj/hardened-dev:master commit in: sys-devel/gcc/ Magnus Granberg
2016-05-05 20:04 Magnus Granberg
2016-05-04 19:24 Anthony G. Basile
2016-05-04 19:14 Magnus Granberg
2013-08-11 16:14 Magnus Granberg
2013-03-26 1:27 Magnus Granberg
2013-03-23 22:52 Magnus Granberg
2013-03-17 0:14 Magnus Granberg
2013-03-17 0:11 Magnus Granberg
2013-03-12 1:43 Magnus Granberg
2013-03-11 23:01 Magnus Granberg
2013-03-10 22:21 Magnus Granberg
2013-02-25 23:01 Magnus Granberg
2013-02-24 22:42 Magnus Granberg
2012-04-17 17:46 Magnus Granberg
2012-04-05 23:40 Magnus Granberg
2012-01-24 20:26 Magnus Granberg
2012-01-17 18:09 Magnus Granberg
2012-01-17 18:05 Magnus Granberg
2011-03-26 16:23 Magnus Granberg
2011-03-07 13:52 Magnus Granberg
2011-03-06 0:15 Magnus Granberg
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=1333741177.c104a5cc32ffdd07592093b1545adc55980e8e62.zorry@gentoo \
--to=zorry@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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