From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: RFC: news item for the 17.0 profiles
Date: Wed, 11 Oct 2017 03:31:55 +0000 (UTC) [thread overview]
Message-ID: <pan$4e236$404ca5e0$141d4884$daba07dd@cox.net> (raw)
In-Reply-To: 3021925.THqB1NeHr9@pinacolada
Andreas K. Huettel posted on Tue, 10 Oct 2017 21:02:32 +0200 as excerpted:
> Am Dienstag, 10. Oktober 2017, 04:10:13 CEST schrieb Duncan:
>
>> One thing isn't clear here. Is this sequence necessary due to the
>> profile switch itself, because the /profile/ enables PIE by default, or
>> is it gcc-6.4+ that enables PIE, and the profile simply forces the PIE
>> default by forcing gcc-6.4+?
>
> Switching the profile changes the settings for building gcc (it switches
> a use-flag from forced-off to forced-on). A gcc-6 built with the 17.0
> profiles will produce PIE executables by default, a gcc-6 built with
> the 13.0 profiles will not.
>
> I've added this paragraph:
> # Switching the profile modifies the settings of GCC 6 to generate
> # PIE executables by default; thus, you need to do the rebuilds
> # even if you already used GCC 6 beforehand.
Thanks. Much clearer now. =:^)
(And I'll have some rebuilding to do.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-10-11 3:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 20:58 [gentoo-dev] RFC: news item for the 17.0 profiles Andreas K. Huettel
2017-10-09 21:40 ` Pacho Ramos
2017-10-09 22:23 ` Toralf Förster
2017-10-10 7:04 ` Pacho Ramos
2017-10-09 23:15 ` Magnus Granberg
2017-10-10 18:56 ` Andreas K. Huettel
2017-10-10 21:27 ` Nils Freydank
2017-11-29 22:56 ` Toralf Förster
2017-10-10 2:10 ` [gentoo-dev] " Duncan
2017-10-10 19:02 ` Andreas K. Huettel
2017-10-11 3:31 ` Duncan [this message]
2017-10-12 7:11 ` Duncan
2017-10-10 7:51 ` [gentoo-dev] " Kent Fredric
2017-10-10 19:05 ` Andreas K. Huettel
2017-10-10 19:16 ` [gentoo-dev] RFC v2: " Andreas K. Huettel
2017-10-10 19:28 ` Alec Warner
2017-10-11 3:56 ` [gentoo-dev] " Duncan
2017-10-11 4:24 ` Alec Warner
2017-10-12 22:51 ` Andreas K. Huettel
2017-10-13 3:02 ` Duncan
2017-10-11 4:41 ` [gentoo-dev] " Walter Dnes
2017-10-11 20:33 ` Walter Dnes
2017-10-11 23:28 ` Brian Evans
2017-10-12 1:38 ` Walter Dnes
2017-10-12 22:55 ` Andreas K. Huettel
2017-10-11 12:10 ` Aaron W. Swenson
2017-10-11 16:45 ` Robin H. Johnson
2017-10-12 22:56 ` Andreas K. Huettel
2017-11-28 10:14 ` [gentoo-dev] " Kristian Fiskerstrand
2017-11-28 11:43 ` [gentoo-dev] " Dirkjan Ochtman
2017-11-28 21:52 ` Andreas K. Huettel
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='pan$4e236$404ca5e0$141d4884$daba07dd@cox.net' \
--to=1i5t5.duncan@cox.net \
--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