From: Joseph Myers <joseph@codesourcery.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
Magnus Granberg <zorry@gentoo.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: PING^3: [PATCH]: New configure options that make the compiler use -fPIE and -pie as default option
Date: Thu, 21 May 2015 17:19:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1505211714550.17178@digraph.polyomino.org.uk> (raw)
In-Reply-To: <yddtwv6t3wp.fsf@lokon.CeBiTec.Uni-Bielefeld.DE>
On Thu, 21 May 2015, Rainer Orth wrote:
> @@ -1864,6 +1873,12 @@ libgcc.mvars: config.status Makefile specs xgcc$(exeext)
> echo GCC_CFLAGS = '$(GCC_CFLAGS)' >> tmp-libgcc.mvars
> echo INHIBIT_LIBC_CFLAGS = '$(INHIBIT_LIBC_CFLAGS)' >> tmp-libgcc.mvars
> echo TARGET_SYSTEM_ROOT = '$(TARGET_SYSTEM_ROOT)' >> tmp-libgcc.mvars
> + if test @enable_default_pie@ = yes; then \
> + NO_PIE_CFLAGS="-fno-PIE"; \
>
> Why literal -fno-PIE instead of @NO_PIE_CFLAGS@?
Because this is for the target, but @NO_PIE_CFLAGS@ is for the host.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2015-05-21 17:16 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 17:31 H.J. Lu
2015-03-06 20:22 ` Magnus Granberg
2015-03-06 20:25 ` H.J. Lu
2015-05-07 21:17 ` Joseph Myers
2015-05-08 17:35 ` H.J. Lu
2015-05-18 22:53 ` Magnus Granberg
2015-05-19 1:25 ` Joseph Myers
2015-05-19 1:34 ` H.J. Lu
2015-05-19 15:27 ` Joseph Myers
2015-05-19 15:33 ` H.J. Lu
2015-05-19 15:33 ` Paul_Koning
2015-05-19 15:43 ` H.J. Lu
2015-05-19 15:37 ` Joseph Myers
2015-05-19 19:33 ` H.J. Lu
2015-05-20 21:29 ` Joseph Myers
2015-05-20 23:01 ` Hans-Peter Nilsson
2015-05-20 23:54 ` H.J. Lu
2015-05-21 14:42 ` Rainer Orth
2015-05-21 17:19 ` Joseph Myers [this message]
2015-05-21 17:57 ` H.J. Lu
2015-06-03 12:48 ` Rainer Orth
[not found] ` <CAMe9rOpZow4w3zcycLoTb5LZdLKP2QWNpsU5oLMJCyZGUTd1fg@mail.gmail.com>
[not found] ` <87vbflkh05.fsf@igel.home>
[not found] ` <CAMe9rOr0SApdtzeOrc-uNDRH8=z6c4EzHUkyXmERW_q9BYjrAQ@mail.gmail.com>
[not found] ` <87k2w1k54t.fsf@igel.home>
2015-05-22 15:39 ` Fwd: " H.J. Lu
2015-05-26 22:42 ` Bill Schmidt
2015-05-26 22:53 ` Bill Schmidt
2015-05-27 15:42 ` Peter Bergner
2015-05-27 15:59 ` H.J. Lu
2015-05-27 16:17 ` Peter Bergner
2015-05-27 16:34 ` H.J. Lu
2015-05-27 17:43 ` David Edelsohn
2015-05-27 17:44 ` H.J. Lu
2015-05-30 15:45 ` Andreas Schwab
2015-05-30 16:24 ` H.J. Lu
2015-05-30 16:44 ` Andreas Schwab
2015-05-30 17:04 ` H.J. Lu
2015-05-30 20:08 ` Andreas Schwab
2015-05-30 21:42 ` H.J. Lu
2015-05-31 0:52 ` Andreas Schwab
2015-05-31 7:13 ` H.J. Lu
2015-05-31 8:23 ` Andreas Schwab
2015-05-31 15:52 ` H.J. Lu
2015-05-30 20:04 ` Andreas Schwab
2015-05-30 21:08 ` Andreas Schwab
2015-10-23 11:57 ` Marcus Shawcroft
2015-10-23 12:44 ` H.J. Lu
2015-10-23 14:27 ` Marcus Shawcroft
2015-10-28 16:06 ` Marcus Shawcroft
2015-10-29 11:02 ` Richard Earnshaw
2015-10-29 11:18 ` H.J. Lu
2015-06-10 13:26 ` Rainer Orth
2015-05-26 23:09 ` Matthew Fortune
2015-05-27 2:49 ` Matthew Fortune
2015-05-27 4:59 ` H.J. Lu
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=alpine.DEB.2.10.1505211714550.17178@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=zorry@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).