From: Paul Sopka <psopka@sopka.ch>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
Date: Thu, 4 Apr 2024 22:32:37 +0200 [thread overview]
Message-ID: <be8fa0a2-2162-4f29-89df-1ba9ab0c21ab@sopka.ch> (raw)
In-Reply-To: <4891397.GXAFRqVoOG@rogueboard>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
On 04.04.24 00:44, Michael wrote:
> No, this is not normal. I wonder if your make.conf settings are correct.
> Start with some safe CFLAGS as suggested here:
>
> https://wiki.gentoo.org/wiki/Safe_CFLAGS
>
> Then use the package 'app-portage/cpuid2cpuflags' to set the correct CPU
> flags:
>
> https://wiki.gentoo.org/wiki/CPU_FLAGS_*
>
> At this point you should be able to use gcc with no further problems. You can
> try to optimise your settings further by taking a look at suggestions here:
>
> https://wiki.gentoo.org/wiki/GCC_optimization
A little correction, even though the "-march=" change removed the
warning gcc threw, it unfortunately didn't solve the issue. I just
recompiled dev-lang/nasm, and after that recompiled libjpeg-turbo, and I
have the same hang on "Detecting C compiler ABI info" again.
Good night
Nanderty
[-- Attachment #2: Type: text/html, Size: 1517 bytes --]
next prev parent reply other threads:[~2024-04-04 20:32 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
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 [this message]
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=be8fa0a2-2162-4f29-89df-1ba9ab0c21ab@sopka.ch \
--to=psopka@sopka.ch \
--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