public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] switch to profile 17.0 complete, completely painless
Date: Sat, 09 Dec 2017 02:36:05 +0100	[thread overview]
Message-ID: <8337286.2jSNpyI8kv@thetick> (raw)
In-Reply-To: <bac0cb6f-8d89-12fe-fd83-cebc2a6e3e3e@st.com>

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

Am Mittwoch, 6. Dezember 2017, 08:00:40 CET schrieb Raffaele Belardi:
> One (~x86) LXDE system completed the switch with no problem, the other
> (~amd64) built all except two packaged (sdlmame and torcs) which did not
> build with gcc-7.2 even before the switch to 17.0.
> 
> Gentoo devs and arch testers did a good job as usual.
> 
> I'll do the switch on the Gnome system in the next days but up to now I can
> say that the switch to 17.0 is a _lot_ less painful than switching major
> compiler version.
> 
> raffaele

I'll add my support for this, the migration was almost completely painless on 
all three of my systems.  There were only a few exceptions:

- I hit the aforementioned cdrdao failure (which I opted to solve via USE 
flag).

- On my laptop I hit the ICU incompatibility with qtwebengine because I had 
firefox install with USE="system-icu" (which was masked at some point in the 
13.0 profiles, which is why I didn't hit this until now), so I unset the USE 
flag again, but that caused some post-migration emerging, which was annoying, 
but not horrible.

- On my desktop rust failed for some reason (almost at the end, of course, 
when building rustdoc), but simply emerging it again afterwards worked.

- On my desktop I also hit the mupen64plus-ui-console build failure.

Note that all of these have open bugs (except for the rust one, but I expect 
that simply came from an inconsistency due to the unfinished "emerge -e 
@world", or a random bitflip, or something similarly ephemeral).

(Oh, and libsidplay failed because its maintainer is apparently too busy to 
fix its incompatibility with app-shells/dash, but that had nothing to do with 
the migration per se.)

I'll also add -- not because I was worried about it but because the 
possibility was mentioned in another thread -- that I can't say I'm noticing 
any performance hits, even on my 11 year old Athlon64 X2.  (IIUC, per the GCC 
manual, PIC and PIE only affect startup time, not runtime, so this result 
should be expected.)

-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

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

      parent reply	other threads:[~2017-12-09  1:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06  7:00 [gentoo-user] switch to profile 17.0 complete, completely painless Raffaele Belardi
2017-12-06  7:18 ` Dale
2017-12-06  8:25   ` Neil Bothwick
2017-12-06 15:38   ` Andrés Becerra Sandoval
2017-12-06 15:49     ` Dale
2017-12-06 16:19     ` Helmut Jarausch
2017-12-06 16:40       ` Andrés Becerra Sandoval
2017-12-06 16:20     ` Alan McKinnon
2017-12-06 23:09       ` Neil Bothwick
2017-12-07  4:40     ` Dale
2017-12-06 15:36 ` Daniel Frey
2017-12-06 16:41   ` Mick
2017-12-06 19:34     ` Daniel Frey
2017-12-09  1:36 ` Marc Joliet [this message]

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=8337286.2jSNpyI8kv@thetick \
    --to=marcec@gmx.de \
    --cc=gentoo-user@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