From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
Date: Wed, 03 Apr 2024 08:40:35 +0100 [thread overview]
Message-ID: <4911228.31r3eYUQgx@rogueboard> (raw)
In-Reply-To: <2f63f3b9-a390-4e61-933f-2049189198c9@sopka.ch>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
On Wednesday, 3 April 2024 06:24:53 BST Paul Sopka wrote:
> On 02.04.24 21:43, Paul Sopka wrote:
> > On 02.04.24 20:50, J. Roeleveld wrote:
> >> Did you upgrade GCC recently?
> >> If yes, did you follow the gcc-upgrade guide:
> >>
> >> https://wiki.gentoo.org/wiki/Upgrading_GCC
> >>
> >> ?
> >
> > Thank you for your answer Joost.
> >
> > As far as I know, I didn't upgrade GCC recently. I just rebuilt
> > libtool to be sure, but that didn't help.
> >
> > Nanderty
>
> I rebuilt with emptytree over night from tty. The system didn't crash,
> but it hung up at the first program to use this, media-libs/libjpeg-turbo.
In case you haven't done it yet, if you rebuild the toolchain things should
hopefully self-correct on your system:
emerge --sync
emerge -1av sys-devel/binutils
emerge -1av --nodeps sys-devel/gcc
Use 'gcc-config -l' to check you are using the correct gcc version.
emerge -1av sys-libs/glibc
emerge -1av dev-build/libtool
env-update && source /etc/profile
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-04-03 7:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 14:11 [gentoo-user] System crash on "Detecting C compiler ABI info" Paul Sopka
2024-04-02 18:50 ` J. Roeleveld
2024-04-02 19:43 ` Paul Sopka
2024-04-03 5:24 ` Paul Sopka
2024-04-03 7:40 ` Michael [this message]
2024-04-03 18:20 ` Paul Sopka
2024-04-03 22:44 ` Michael
2024-04-04 20:17 ` Paul Sopka
2024-04-04 20:32 ` Paul Sopka
2024-04-04 22:55 ` Michael
2024-04-05 6:31 ` Paul Sopka
2024-04-05 6:34 ` Paul Sopka
2024-04-05 9:01 ` Michael
2024-04-08 6:29 ` Paul Sopka
2024-04-03 12:44 ` James Massa
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=4911228.31r3eYUQgx@rogueboard \
--to=confabulate@kintzios.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