From: lee <lee@yagibdah.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Gcc 5.3
Date: Fri, 01 Jan 2016 11:37:46 +0100 [thread overview]
Message-ID: <877fjt1t6t.fsf@heimdali.yagibdah.de> (raw)
In-Reply-To: 13319502.2dI8TEsWB0@bluering
Paul Colquhoun <paulcol@andor.dropbear.id.au> writes:
> On Wed, 30 Dec 2015 17:32:44 lee wrote:
>> Neil Bothwick <neil@digimed.co.uk> writes:
>> > On Tue, 29 Dec 2015 19:21:01 +0100, lee wrote:
> [...]
>> >> 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.
>>
>> Well, yes, but what if want to install a package that hasn't been
>> installed yet, or re-emerge an installed package with different USE
>> flags, after updating the portage tree? Will a more recent version be
>> installed than would have been installed before the tree was updated,
>> maybe updating other packages to more recent versions because they are
>> needed for the new package?
>
>
> You have a couple of options.
>
> First, start with "emerge -p whatever" and see what update would happen with
> no adjustments.
>
> Then try again, but specify the version you want and see if that works:
> "emerge -p =whatever-1.2.3"
>
> If it is still trying to install updated versions of libraries or other
> dependencies, make a file like /etc/portage/package.mask/whatever and block
> anything higher than the library/dependency versions you already have.
>
> A bit more work, but probably not much.
>
> However, if you get too far behind, the versions you want may have been
> removed from the portage tree. This is still not a deal breaker. Old ebuilds
> are available from the Gentoo attic at https://sources.gentoo.org/cgi-bin/viewvc.cgi and can be installed in a local overlay. (I put mine in
> /usr/local/portage). Just put "PORTDIR_OVERLAY=/usr/local/portage" into
> /etc/portage/make/conf and you should be set.
>
> You could also use the local overlay to just add the updated ebuilds for
> things you do want to upgrade (and required dependency upgrades, etc) but I
> think that would quickly become very unwieldy.
Thank you for the explanation.
I've installed gcc 5.2.0 and am running into trouble when trying to
compile the test application. That just won't work.
It also runs out of memory too easily.
OTOH, I've compiled a kernel with it (unless the compilation somehow
picks a different version automatically), and it works fine.
>> > Exactly, run gcc-config, compile/emerge the program, run gcc-config again.
>>
>> And what about ccache? Will it use the new version automatically and
>> detect that the compiler version has changed so that files in the cache
>> need to be recompiled?
To answer my own question: That also works without any further ado.
prev parent reply other threads:[~2016-01-01 10:44 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
2015-12-30 16:32 ` lee
2015-12-30 22:33 ` Paul Colquhoun
2016-01-01 10:37 ` lee [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=877fjt1t6t.fsf@heimdali.yagibdah.de \
--to=lee@yagibdah.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