public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: gevisz <gevisz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrading gcc from 6.4 to 7.3
Date: Wed, 20 Jun 2018 15:01:19 +0300	[thread overview]
Message-ID: <CA+t6X7fsXFW7+-CXZGYP1_-Pr7gVAc0H75UC7zxODKDbvMmzUA@mail.gmail.com> (raw)
In-Reply-To: <3376641.ueHKpIXWU0@dell_xps>

2018-06-20 14:16 GMT+03:00 Mick <michaelkintzios@gmail.com>:
> On Wednesday, 20 June 2018 11:43:32 BST gevisz wrote:
>> After updating portage tree today, portage
>> suggested to upgrade gcc from 6.4 to 7.3
>> version what I have done just now.
>>
>> Nevertheless,
>> # gcc-config --list-profiles
>>  [1] x86_64-pc-linux-gnu-6.4.0 *
>>  [2] x86_64-pc-linux-gnu-7.3.0
>> shows that I still have version 6.4 as a default.
>
> I'm on gcc-7.3.0-r3 and have not noticed any problems on 3 boxen so far.
>
>
>> As https://wiki.gentoo.org/wiki/Upgrading_GCC
>> still do not have any specific instructions on
>> switching to gcc version 7.3, I am still afread
>> of switching to gcc version 7.3 and would like
>> to ask if anybody encountered some problem
>> after switching to gcc version 7.3 and which
>> packages should be rebuild after such switching.
>>
>> Thank you in advance for your help.
>
> I didn't have to rebuild anything, but if you have reasons to fear breakage
> you can rebuild your toolchain:
>
> 1. Use gcc-config to select x86_64-pc-linux-gnu-7.3.0
> 2. Re-source /etc/profile by running in your current console/terminal:
>     . /etc/profile
> 3. Re-emerge libtool:
>     emerge -1 sys-devel/libtool
> 4. Re-emerge the following packages in this order:
>     emerge -1 sys-devel/gcc-7.3.0-r3
>     emerge -1 sys-devel/binutils
>     emerge -1 sys-libs/glibc
> 5. You could if you want re-emerge your entire system, 'emerge -e @world' or
> if you would rather conserve electricity wait as different packages come up
> for an update over time.
>
> If my experience to date holds true and for a general purpose desktop none of
> the above rebuilds are necessary, other than switching your gcc to 7.3.0.

Thank you for your reply. I do not want to rebuild gcc-7.3 for the second time
today (as far as the temperature in my room is already +30°C). So, I will stick
to your last advice: I will just switch the default gcc version to 7.3
and wait for
problems to appear. :)


  reply	other threads:[~2018-06-20 12:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20 10:43 [gentoo-user] Upgrading gcc from 6.4 to 7.3 gevisz
2018-06-20 11:16 ` Mick
2018-06-20 12:01   ` gevisz [this message]
2018-06-20 12:49     ` gevisz
2018-07-10 12:09       ` gevisz
2018-07-24 19:00   ` gevisz
2018-07-24 19:02     ` gevisz
2018-08-02 11:55       ` Thomas
2018-06-21 21:16 ` 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=CA+t6X7fsXFW7+-CXZGYP1_-Pr7gVAc0H75UC7zxODKDbvMmzUA@mail.gmail.com \
    --to=gevisz@gmail.com \
    --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