From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: news item for the 17.0 profiles
Date: Tue, 10 Oct 2017 20:51:43 +1300 [thread overview]
Message-ID: <20171010205143.34b132db@katipo2.lan> (raw)
In-Reply-To: <1528131.eIYCIZq90I@pinacolada>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
On Mon, 09 Oct 2017 22:58:22 +0200
"Andreas K. Huettel" <dilfridge@gentoo.org> wrote:
> 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.
Just a question that only became apparent to me as I'm trying to
create a "mostly stable" keyworded chroot, but with this change added
to pick up defects:
Are there any specific versions of toolchain modules that should/must be used
in 17.0 to make it work with GCC-6.4.0?
All I did was:
- Forcibly create the profile symlink myself ( as its not visible to me
yet with eselect )
- accept-keywords for gcc
- Followed remaining instructions.
And hopefully that should be sufficient.
binutils: 2.28.1
gcc: 6.4.0
glibc: 2.23-r4
libtool: 2.4.6-r3
I know this is typically a "don't mix ~arch and arch" thing, but I
can't actually test things that will break otherwise :p
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-10 7:52 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
2017-10-12 7:11 ` Duncan
2017-10-10 7:51 ` Kent Fredric [this message]
2017-10-10 19:05 ` [gentoo-dev] " 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=20171010205143.34b132db@katipo2.lan \
--to=kentnl@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