From: antlists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] haven't been able to build android-tools for months
Date: Mon, 6 Sep 2021 21:59:19 +0100 [thread overview]
Message-ID: <556957ae-03db-1890-df8c-712b198b467b@youngman.org.uk> (raw)
In-Reply-To: <12045587-28a3-6fd5-7493-5ffec2da92af@web.de>
On 06/09/2021 20:23, n952162 wrote:
> Aggh!
>
> 00~/adm/gentoo/emerged>eselect gcc list
> [1] x86_64-pc-linux-gnu-9.3.0 *
> [2] x86_64-pc-linux-gnu-10.3.0
>
>
> $ eselect news list | grep gcc
>
> doesn't turn up anything. When should/may one upgrade?
>
> Thank you for the tip! That's surely what's going on.
Others may chime in and say I'm wrong, but my immediate reaction would
be an "eselect gcc set 2" to upgrade the active gcc. An "emerge
--depclean" without that could easily leave you with a broken system -
probably easy enough to fix but still a nightmare until you realise
what's happened ...
If there's no news, then the change *should* not be a problem.
And if you're at all worried, follow that with an "emerge -e @system".
Provide it runs successfully ... you will have a working system, even if
bits of it break. Only downside, it will probably take quite a while to
run ...
Cheers,
Wol
next prev parent reply other threads:[~2021-09-06 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 18:14 [gentoo-user] haven't been able to build android-tools for months n952162
2021-09-06 18:19 ` cal
2021-09-06 19:23 ` n952162
2021-09-06 20:59 ` antlists [this message]
2021-09-06 21:04 ` cal
2021-09-07 18:02 ` [gentoo-user] haven't been able to build android-tools for months [ RESOLVED ] n952162
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=556957ae-03db-1890-df8c-712b198b467b@youngman.org.uk \
--to=antlists@youngman.org.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