public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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: Wed, 3 Apr 2024 20:20:27 +0200	[thread overview]
Message-ID: <1bf8f2ff-2143-4c1e-ac25-584a87ef1951@sopka.ch> (raw)
In-Reply-To: <4911228.31r3eYUQgx@rogueboard>

On 03.04.24 09:40, Michael wrote:
> 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
>
Good evening Michael

Thank you for your suggestions, I tried them, but unfortunately it 
didn't help.

Also, i found out that removing CPU_FLAGS_X86 made the issue disappear, 
but another issue appeared later. I experience a similar hang, at "-- 
Looking for a ASM_NASM compiler".

Further, compiling GCC throws the following warnings:

  * QA Notice: Installing libtool files (.la) without corresponding 
static libraries!
  *   /usr/libexec/gcc/x86_64-pc-linux-gnu/13/liblto_plugin.la
  * QA Notice: Found the following implicit function declarations in 
configure logs:
  * 
/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/32/libgfortran/config.log:4628 
- fpsetmask
  * 
/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libgfortran/config.log:4536 
- fpsetmask
  * Check that no features were accidentally disabled.
  * See https://wiki.gentoo.org/wiki/Modern_C_porting.
  * QA Notice: Package triggers severe warnings which indicate that it
  *            may exhibit random runtime failures.
  * 
/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec.h:316: 
warning: ‘free’ called on unallocated object ‘accesses’ 
[-Wfree-nonheap-object]
  * 
/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec.h:316:10: 
warning: ‘free’ called on unallocated object ‘dest_bbs’ 
[-Wfree-nonheap-object]
  * 
/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec.h:316: 
warning: ‘free’ called on unallocated object ‘accesses’ 
[-Wfree-nonheap-object]
  * 
/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec.h:316:10: 
warning: ‘free’ called on unallocated object ‘dest_bbs’ 
[-Wfree-nonheap-object]
  * 
/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/libsanitizer/hwasan/hwasan.cpp:539:52: 
warning: format ‘%zd’ expects a matching ‘signed size_t’ argument 
[-Wformat=]
  * Please do not file a Gentoo bug and instead report the above QA
  * issues directly to the upstream developers of this software.
  * Homepage: https://gcc.gnu.org/

Is this normal?

Hope you all have a nice evening

Nanderty



  reply	other threads:[~2024-04-03 18:20 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 [this message]
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=1bf8f2ff-2143-4c1e-ac25-584a87ef1951@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