public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "robert at linuxfromscratch dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/7065] Support building glibc with -fstack-protector or -fstack-protector-all
Date: Thu, 04 Jun 2009 22:25:00 -0000	[thread overview]
Message-ID: <20090604222535.24631.qmail@sourceware.org> (raw)
In-Reply-To: <20081204003831.7065.nix@esperi.org.uk>


------- Additional Comments From robert at linuxfromscratch dot org  2009-06-04 22:25 -------
I've been using a compromise. Glibc's programs can be compiled 
with -fstack-protector-all, or whatever other options you may want 
(-D_FORTIFY_SOURCE=2, -fPIE, etc), but not the libraries. I use the configparms 
file and set build-programs=no to build the libraries 
without -fstack-protector, then remove build-programs=no and add 'CFLAGS 
+= -fstack-protector-all' to configparms. No patches needed, test suites pass 
(remove -fstack-protector during the test suite), no crashes.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=7065

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


      parent reply	other threads:[~2009-06-04 22:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04  0:39 [Bug libc/7065] New: " nix at esperi dot org dot uk
2008-12-04  0:47 ` [Bug libc/7065] " drepper at redhat dot com
2008-12-04  0:54 ` nix at esperi dot org dot uk
2008-12-04  0:57 ` nix at esperi dot org dot uk
2008-12-05  0:32 ` zorry at ume dot nu
2008-12-10 17:10 ` rsa at us dot ibm dot com
2008-12-10 18:52 ` rsa at us dot ibm dot com
2008-12-13 19:04 ` nix at esperi dot org dot uk
2008-12-14 11:34 ` atoth at atoth dot sote dot hu
2008-12-14 14:01 ` xake at rymdraket dot net
2008-12-27  3:15 ` vapier at gentoo dot org
2009-06-04 22:25 ` robert at linuxfromscratch dot org [this message]

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=20090604222535.24631.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).