public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Cc: PR Gentoo <pr@gentoo.org>
Subject: [gentoo-dev] RFC: news item for the 17.0 profiles
Date: Mon, 09 Oct 2017 22:58:22 +0200	[thread overview]
Message-ID: <1528131.eIYCIZq90I@pinacolada> (raw)

[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]

=====================================
Title: New 17.0 profiles in the Gentoo repository
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Posted: xxxxxxx
Revision: 1
News-Item-Format: 2.0
Display-If-Installed: >=sys-devel/gcc-6.4.0

We have just added a new set of profiles with release version 17.0
to the Gentoo repository. These bring two changes:
1) The default C++ language version for applications is now C++14.
   This change is mostly relevant to Gentoo developers. It also
   means, however, that compilers earlier than GCC 6 are masked 
   and not supported for use as a system compiler anymore. Feel 
   free to unmask them if you need them for specific applications.
2) Where supported, GCC will now build position-independent
   executables (PIE) by default. This improves the overall
   security fingerprint. The switch from non-PIE to PIE binaries,
   however, requires some steps by users, as detailed below.

Please consider switching from your current 13.0 profile to the
corresponding 17.0 profile soon after GCC-6.4.0 has been 
stabilized on your architecture. The 13.0 profiles will be deprecated 
and removed in the near future.

Switching involves the following steps: 
If not already done,
* Use gcc-config to select gcc-6.4.0 or later as system compiler
* Re-source /etc/profile:
    . /etc/profile
* Re-emerge libtool
Then, 
* Select the new profile with eselect
* Re-emerge, in this sequence, gcc, binutils, and glibc
    emerge -1 sys-devel/gcc:6.4.0
    emerge -1 sys-devel/binutils
    emerge -1 sys-libs/glibc
* Rebuild your entire system
    emerge -e world

If you do not follow these steps you may get spurious build
failures when the linker tries unsuccessfully to combine non-PIE
and PIE code.
=====================================

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

             reply	other threads:[~2017-10-09 20:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 20:58 Andreas K. Huettel [this message]
2017-10-09 21:40 ` [gentoo-dev] RFC: news item for the 17.0 profiles 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
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=1528131.eIYCIZq90I@pinacolada \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=pr@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