public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@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 21:05:53 +0200	[thread overview]
Message-ID: <4668243.2CRj0u1zfO@pinacolada> (raw)
In-Reply-To: <20171010205143.34b132db@katipo2.lan>

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

Am Dienstag, 10. Oktober 2017, 09:51:43 CEST schrieb Kent Fredric:
> 
> 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?
> 

Not that I know of. I'd use most recent stable though.

(And glibc-2.25 will most likely become stable before gcc-6.)

> 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.

That should be perfectly fine.

> 
> 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

The whole "don't mix ~arch and arch" credo is in my opinion a bit silly. If 
mixing leads to bugs, these should be documented and fixed, if only with a 
version dependency.

-- 
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-10 19:06 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 ` [gentoo-dev] " Kent Fredric
2017-10-10 19:05   ` Andreas K. Huettel [this message]
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=4668243.2CRj0u1zfO@pinacolada \
    --to=dilfridge@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