From: "Magnus Granberg" <zorry@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-gccpatchset:master commit in: upstream/
Date: Wed, 27 Apr 2011 11:12:58 +0000 (UTC) [thread overview]
Message-ID: <de738d984c6dcabfd2ef044227333474a3115738.zorry@gentoo> (raw)
commit: de738d984c6dcabfd2ef044227333474a3115738
Author: Magnus Granberg <zorry <AT> gentoo <DOT> org>
AuthorDate: Wed Apr 27 11:12:41 2011 +0000
Commit: Magnus Granberg <zorry <AT> gentoo <DOT> org>
CommitDate: Wed Apr 27 11:12:41 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-gccpatchset.git;a=commit;h=de738d98
Added the configure.ac patch for upstream fist rev
---
upstream/configure.ac.patch | 43 +++++++++++++++++++++++++++++++++++++++++++
1 files changed, 43 insertions(+), 0 deletions(-)
diff --git a/upstream/configure.ac.patch b/upstream/configure.ac.patch
new file mode 100644
index 0000000..cfee97f
--- /dev/null
+++ b/upstream/configure.ac.patch
@@ -0,0 +1,43 @@
+2011-04-27 Magnus Granberg <zorry@gentoo.org>
+
+ * configure Add --enable-espf. Add -fno-stack-protector
+ to stage1_cflags.
+--- a/configure.ac 2011-04-18 23:27:00.000000000 +0200
++++ b/configure.ac 2011-04-27 12:47:11.351473240 +0200
+@@ -419,6 +419,25 @@
+ noconfigdirs="$noconfigdirs gnattools"
+ fi
+
++# Check whether --enable-espf was given and target have the support.
++AC_ARG_ENABLE([espf],
++[AS_HELP_STRING([--enable-espf],
++ [Enable Stack protector, Position independent executable and
++ Fortify_sources as default if we have suppot for it when compiling
++ and link with -z relro and -z now as default.
++ Linux targets supported x86_64.])],
++[
++ case $target in
++ x86_64*-*-linux*)
++ enable_espf=yes
++ ;;
++ *)
++ AC_MSG_WARN([*** --enable-espf is not supported on this $target target.])
++ ;;
++ esac
++])
++AC_SUBST([enable_espf])
++
+ AC_ARG_ENABLE(libssp,
+ [AS_HELP_STRING([--enable-libssp], [build libssp directory])],
+ ENABLE_LIBSSP=$enableval,
+@@ -3152,6 +3171,10 @@
+ esac ;;
+ esac
+
++# Disable -fstack-protector on stage1
++if test x$enable_espf = xyes; then
++ stage1_cflags="$stage1_cflags -fno-stack-protector"
++fi
+ # This is aimed to mimic bootstrap with a non-GCC compiler to catch problems.
+ if test "$GCC" = yes -a "$ENABLE_BUILD_WITH_CXX" != yes; then
+ saved_CFLAGS="$CFLAGS"
next reply other threads:[~2011-04-27 11:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 11:12 Magnus Granberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-22 0:27 [gentoo-commits] proj/hardened-gccpatchset:master commit in: upstream/ Magnus Granberg
2011-06-23 18:15 Magnus Granberg
2011-06-24 9:36 Magnus Granberg
2011-06-24 13:51 Magnus Granberg
2011-06-24 14:15 Magnus Granberg
2011-06-24 14:32 Magnus Granberg
2011-06-24 14:45 Magnus Granberg
2012-04-08 12:36 Magnus Granberg
2012-04-08 13:00 Magnus Granberg
2012-07-25 15:09 Magnus Granberg
2012-07-30 21:05 Magnus Granberg
2012-08-01 18:35 Magnus Granberg
2012-08-08 16:05 Magnus Granberg
2012-08-21 20:10 Magnus Granberg
2012-08-22 19:19 Magnus Granberg
2012-08-27 23:34 Magnus Granberg
2012-10-07 16:50 Magnus Granberg
2012-10-07 16:54 Magnus Granberg
2013-11-10 10:23 Magnus Granberg
2013-11-13 21:00 Magnus Granberg
2013-11-13 21:13 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=de738d984c6dcabfd2ef044227333474a3115738.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