From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Gcc 5.3
Date: Tue, 29 Dec 2015 22:48:51 +0000 [thread overview]
Message-ID: <20151229224851.60a9e287@digimed.co.uk> (raw)
In-Reply-To: <87lh8dktf6.fsf@heimdali.yagibdah.de>
[-- Attachment #1: Type: text/plain, Size: 2237 bytes --]
On Tue, 29 Dec 2015 19:21:01 +0100, lee wrote:
> > As 4.9.3 is marked stable, I guess that's what'd you get per
> > default.
>
> 4.8.5
>
> I'd have to run emerge --sync to know about more recent versions. How
> is that supposed to be used, btw? I only run that when I do want to
> update everything. Now if I didn't want to update anything but gcc,
> could I run emerge --sync and install gcc 5.x without having trouble
Emerge --sync only updates the portage tree, so
emerge --sync
emerge -a sys-devel/gcc:5
> with anything else I might install before actually updating everything?
> So if I'd never explicitly update everything but run emerge --sync
> frequently, things would be updated over time, occasionally?
No, nothing would get updated. To do that you need to run emerge @world
after emerge --sync.
> > Stuff compiled with older gcc's should run with newer libgcc*[0], but
> > stuff compililed with a newer gcc might not run with the older
> > libgcc*. Same goes, with more problems IIRC, for libstdc++.
> > So beware of that. Apart from that? I'm not aware of problems.
>
> Uhm ... So I might break the system by switching between compiler
> versions?
That's highly unlikely as software that has been compiled with the old
compiler will still work. You may find that some programs fail to
recompile with the new compiler, but I didn't experience that with the
4.9>5 step, although I had some that would build with 4.8 but not 4.9.
I have an application which I would like to compile with gcc
> 5.x just to see if that's even possible. I could switch, try it, and
> then switch back.
Exactly, run gcc-config, compile/emerge the program, run gcc-config again.
> > BTW: why is gcc not also handled via eselect? Even if that'd just
> > call gcc-config?
There was a gcc eselect module but it was dropped in favour of gcc-config
as it didn't do what was needed of it. This is not unique to gcc, we also
have binutils-config. As to why no one has written an eselect wrapper for
either of these, I'd guess it's harder than it sounds or no one who can
do it feels the need.
--
Neil Bothwick
Windows Error #02: Multitasking attempted. System confused.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-12-29 22:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 15:18 [gentoo-user] Gcc 5.3 Alan Grimes
2015-12-24 15:39 ` Stanislav Nikolov
2015-12-24 16:05 ` Alan Grimes
2015-12-24 20:17 ` David Haller
2015-12-25 16:01 ` Alan Grimes
2015-12-24 22:05 ` Paul Colquhoun
2015-12-25 12:47 ` Andreas K. Huettel
2015-12-25 15:42 ` Alan Grimes
2015-12-25 20:40 ` [gentoo-user] " walt
2015-12-26 3:00 ` Paul Colquhoun
2015-12-26 5:44 ` Paul Colquhoun
2016-01-01 15:51 ` Stefan G. Weichinger
2015-12-26 6:25 ` David Haller
2015-12-26 8:40 ` Philip Webb
2015-12-28 8:17 ` Andrew Savchenko
2015-12-29 12:52 ` lee
2015-12-29 14:54 ` David Haller
2015-12-29 18:21 ` lee
2015-12-29 22:48 ` Neil Bothwick [this message]
2015-12-30 16:32 ` lee
2015-12-30 22:33 ` Paul Colquhoun
2016-01-01 10:37 ` lee
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=20151229224851.60a9e287@digimed.co.uk \
--to=neil@digimed.co.uk \
--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