From: cal <cal@mail.meme.technology>
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 14:04:25 -0700 [thread overview]
Message-ID: <e01291e2-29c1-eba1-5eba-63c298dbd0ab@mail.meme.technology> (raw)
In-Reply-To: <12045587-28a3-6fd5-7493-5ffec2da92af@web.de>
On 9/6/21 12:23 PM, n952162 wrote:
>>
>> Given the error message implies a compiler error, perhaps try upgrading
>> sys-devel/gcc first?
>>
>
> 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.
https://wiki.gentoo.org/wiki/Upgrading_GCC (note: most of the content
here appears to be related to upgrading to GCC 5.x).
Like the kernel, new versions of GCC are automatically pulled in, but
you have to eselect the new one manually (I don't know the reason; I
assume it is to avoid leaving the user with a broken compiler).
Personally, I just check the emerge output to see if a new version of
GCC was merged, and if so, I eselect it and rebuild libtool as described
on the wiki.
cal
next prev parent reply other threads:[~2021-09-06 21:04 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
2021-09-06 21:04 ` cal [this message]
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=e01291e2-29c1-eba1-5eba-63c298dbd0ab@mail.meme.technology \
--to=cal@mail.meme.technology \
--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