[gentoo-user] System crash on "Detecting C compiler ABI info"

[gentoo-user] System crash on "Detecting C compiler ABI info"

[Paul Sopka]

Hello Gentoo,

my entire system crashes reliably on "Detecting C compiler ABI info" 
when compiling some packages, happened on sci-libs/netcdf and 
media-libs/svt-av1.

I am pretty sure it isn't a hardware instability since I can compile 
everything that doesn't run "Detecting C compiler ABI info" without any 
issues at all.

Does anybody have an idea why this happens?

I wish you all a nice afternoon!

Nanderty

Re: [gentoo-user] System crash on "Detecting C compiler ABI info"

[J. Roeleveld]

On Tuesday, 2 April 2024 16:11:20 CEST Paul Sopka wrote:
> Hello Gentoo,
> 
> my entire system crashes reliably on "Detecting C compiler ABI info"
> when compiling some packages, happened on sci-libs/netcdf and
> media-libs/svt-av1.
> 
> I am pretty sure it isn't a hardware instability since I can compile
> everything that doesn't run "Detecting C compiler ABI info" without any
> issues at all.
> 
> Does anybody have an idea why this happens?
> 
> I wish you all a nice afternoon!
> 
> Nanderty

Did you upgrade GCC recently?
If yes, did you follow the gcc-upgrade guide:

https://wiki.gentoo.org/wiki/Upgrading_GCC

?

--
Joost

Re: [gentoo-user] System crash on "Detecting C compiler ABI info"

[Paul Sopka]

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
>
> ?
>
> --
> Joost

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

Re: [gentoo-user] System crash on "Detecting C compiler ABI info"

[Paul Sopka]

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
>>
>> ?
>>
>> -- 
>> Joost
>
> 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.

Re: [gentoo-user] System crash on "Detecting C compiler ABI info"

[Michael]

[-- 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 --]

Re: [gentoo-user] System crash on "Detecting C compiler ABI info"

[James Massa]

[-- Attachment #1: Type: text/html, Size: 2254 bytes --]

Re: [gentoo-user] System crash on "Detecting C compiler ABI info"

[Paul Sopka]

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

Re: [gentoo-user] System crash on "Detecting C compiler ABI info"

[Michael]

[-- Attachment #1: Type: text/plain, Size: 3362 bytes --]

On Wednesday, 3 April 2024 19:20:27 BST Paul Sopka wrote:
> 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-g
> nu/32/libgfortran/config.log:4628 - fpsetmask
>   *
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-g
> nu/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/libsani
> tizer/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?

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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] System crash on "Detecting C compiler ABI info"

[Paul Sopka]

[-- Attachment #1: Type: text/plain, Size: 1403 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

Thank you for pointing into the right direction.

After changing -march=raptorlake to -march=alderlake on an i5-13600KS 
and running the following three times:

> 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
I don't get the hang at "-- Detecting C compiler ABI info" anymore. It 
now hangs later on "-- Looking for a ASM_NASM compiler".

My CPU_FLAGS_* are correct, I checked them with 
app-portage/cpuid2cpuflags to make sure they are up to date and they were.

Do you have any idea for this?

Thank you

Nanderty

[-- Attachment #2: Type: text/html, Size: 2236 bytes --]

Re: [gentoo-user] System crash on "Detecting C compiler ABI info"

[Paul Sopka]

[-- 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 --]

Re: [gentoo-user] System crash on "Detecting C compiler ABI info"

[Michael]

[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]

On Thursday, 4 April 2024 21:32:37 BST Paul Sopka wrote:
> 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.

Your toolchain is now correct.  Can you show the output of:

equery u media-libs/libjpeg-turbo

and

emerge --info media-libs/libjpeg-turbo

However, it could be this is a bug, you can check here for reports:

https://bugs.gentoo.org/buglist.cgi?quicksearch=media-libs%2Flibjpeg-turbo

If this is the only package you're getting a problem with, you can run:

emerge --resume --skipfirst

to complete your migration to profile 23.0, then try again to emerge libjpeg-
turbo on its own.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] System crash on "Detecting C compiler ABI info"

[Paul Sopka]

On 05.04.24 00:55, Michael wrote:
> Your toolchain is now correct.  Can you show the output of:
>
> equery u media-libs/libjpeg-turbo
>
> and
>
> emerge --info media-libs/libjpeg-turbo
>
> However, it could be this is a bug, you can check here for reports:
>
> https://bugs.gentoo.org/buglist.cgi?quicksearch=media-libs%2Flibjpeg-turbo
>
> If this is the only package you're getting a problem with, you can run:
>
> emerge --resume --skipfirst
>
> to complete your migration to profile 23.0, then try again to emerge libjpeg-
> turbo on its own.

Unfortunately I have this issue with many packages.

I can confirm it with media-libs/libjpeg-turbo:

  * Found these USE flags for media-libs/libjpeg-turbo-3.0.2:
  U I
  + + abi_x86_32  : 32-bit (x86) libraries
  - - java        : Add support for Java
  - - static-libs : Build static versions of dynamic libraries as well

and dev-util/vulkan-headers as well as sci-libs/netcdf:

  * Found these USE flags for sci-libs/netcdf-4.9.2-r1:
  U I
  - - blosc    : Allow using blosc compression via dev-libs/c-blosc
  + + bzip2    : Enable bzip2 compression support
  + - dap      : Support for remote data access with the built-in 
OPeNDAP client
  - - doc      : Add extra documentation (API, Javadoc, etc). It is 
recommended to enable per package instead of globally
  - - examples : Install examples, usually source code
  - - hdf      : Build with HDF4 read capability(sci-libs/hdf, 
sci-libs/hdf5 and sys-libs/zlib required).
  + - hdf5     : Add support for the Hierarchical Data Format v5
  - - mpi      : Add MPI (Message Passing Interface) layer to the apps 
that support it
  - - szip     : Use the szip compression library
  - - test     : Enable dependencies and/or preparations necessary to 
run tests (usually controlled by FEATURES=test but can be toggled 
independently)
  + + zstd     : Enable support for ZSTD compression

My emerge --info media-libs/libjpeg-turbo:

Portage 3.0.63 (python 3.11.8-final-0, default/linux/amd64/23.0, gcc-13, 
glibc-2.39-r2, 6.8.2-gentoo x86_64)
=================================================================
                          System Settings
=================================================================
System uname: 
Linux-6.8.2-gentoo-x86_64-13th_Gen_Intel-R-_Core-TM-_i5-13600KF-with-glibc2.39
KiB Mem:    32699852 total,  27956992 free
KiB Swap:          0 total,         0 free
Timestamp of repository gentoo: Thu, 04 Apr 2024 18:19:20 +0000
Head commit of repository gentoo: 45b6803c7d0c2f6e0bbb7247385e9a3095dc172b

Timestamp of repository guru: Thu, 04 Apr 2024 17:48:38 +0000
Head commit of repository guru: ae5669fdb3157526d19cdfab0661a2719f00170b

Timestamp of repository steam-overlay: Thu, 04 Apr 2024 01:22:27 +0000
Head commit of repository steam-overlay: 
aca6eb772e0d5474b6d44072998af0082f36d08a

Timestamp of repository wayland-desktop: Thu, 04 Apr 2024 01:22:35 +0000
Head commit of repository wayland-desktop: 
559692d775352c785aecfec52d940f20f5c9b800

sh dash 0.5.12
ld GNU ld (Gentoo 2.42 p3) 2.42.0
app-misc/pax-utils:        1.3.7::gentoo
app-shells/bash:           5.2_p26::gentoo
dev-build/autoconf:        2.13-r8::gentoo, 2.72-r1::gentoo
dev-build/automake:        1.16.5-r2::gentoo
dev-build/cmake:           3.29.0::gentoo
dev-build/libtool:         2.4.7-r4::gentoo
dev-build/make:            4.4.1-r1::gentoo
dev-build/meson:           1.4.0-r1::gentoo
dev-java/java-config:      2.3.3-r1::gentoo
dev-lang/perl:             5.38.2-r2::gentoo
dev-lang/python:           3.11.8_p1::gentoo, 3.12.2_p1::gentoo
dev-lang/rust-bin:         1.76.0::gentoo
sys-apps/baselayout:       2.15::gentoo
sys-apps/openrc:           0.53.1::gentoo
sys-apps/sandbox:          2.38::gentoo
sys-devel/binutils:        2.42-r1::gentoo
sys-devel/binutils-config: 5.5::gentoo
sys-devel/clang:           17.0.6::gentoo, 18.1.2::gentoo
sys-devel/gcc:             13.2.1_p20240210::gentoo
sys-devel/gcc-config:      2.11::gentoo
sys-devel/lld:             17.0.6::gentoo
sys-devel/llvm:            17.0.6::gentoo, 18.1.2::gentoo
sys-kernel/linux-headers:  6.8-r1::gentoo (virtual/os-headers)
sys-libs/glibc:            2.39-r2::gentoo
Repositories:

gentoo
     location: /var/db/repos/gentoo
     sync-type: git
     sync-uri: https://github.com/gentoo-mirror/gentoo.git
     priority: -1000
     volatile: False

guru
     location: /var/db/repos/guru
     sync-type: git
     sync-uri: https://github.com/gentoo-mirror/guru.git
     masters: gentoo
     volatile: False

steam-overlay
     location: /var/db/repos/steam-overlay
     sync-type: git
     sync-uri: https://github.com/gentoo-mirror/steam-overlay.git
     masters: gentoo
     volatile: False

wayland-desktop
     location: /var/db/repos/wayland-desktop
     sync-type: git
     sync-uri: https://github.com/gentoo-mirror/wayland-desktop.git
     masters: gentoo
     volatile: False

crossdev
     location: /var/db/repos/crossdev
     masters: gentoo
     priority: 10
     volatile: False

Binary Repositories:

gentoobinhost
     priority: 1
     sync-uri: 
https://gentoo.osuosl.org/releases/amd64/binpackages/23.0/x86-64

ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="*"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=alderlake -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d 
/etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release 
/etc/php/apache2-php8.3/ext-active/ /etc/php/cgi-php8.3/ext-active/ 
/etc/php/cli-php8.3/ext-active/ /etc/php/fpm-php8.3/ext-active/ 
/etc/php/phpdbg-php8.3/ext-active/ /etc/revdep-rebuild /etc/sandbox.d"
CXXFLAGS="-march=alderlake -O2 -pipe"
DISTDIR="/var/cache/distfiles"
ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY 
GDK_PIXBUF_MODULE_FILE GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX 
PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME 
XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR XDG_STATE_HOME"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs 
binpkg-multi-instance buildpkg-live candy config-protect-if-modified 
distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync merge-wait 
multilib-strict network-sandbox news parallel-fetch pid-sandbox 
pkgdir-index-trusted preserve-libs protect-owned 
qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn 
unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="https://mirror.init7.net/gentoo/"
LANG="en_US.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs"
LEX="flex"
MAKEOPTS="--jobs 20 --load-average 20"
PKGDIR="/var/cache/binpkgs"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times 
--omit-dir-times --compress --force --whole-file --delete --stats 
--human-readable --timeout=180 --exclude=/distfiles --exclude=/local 
--exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
SHELL="/bin/bash"
USE="acl amd64 bzip2 cet crypt cups fpm gd gdbm hwaccel iconv ipv6 
libnotify libtirpc lto lzma multilib ncurses nls openmp pam pcre pdo php 
pipewire pulseaudio readline screencast seatd seccomp ssl test-rust udev 
unicode vaapi vulkan wayland xattr zlib zstd" ABI_X86="64" 
ADA_TARGET="gcc_12" APACHE2_MODULES="authn_core authz_core socache_shmcb 
unixd actions alias auth_basic authn_anon authn_dbm authn_file authz_dbm 
authz_groupfile authz_host authz_owner authz_user autoindex cache cgi 
cgid dav dav_fs dav_lock deflate dir env expires ext_filter file_cache 
filter headers include info log_config logio mime mime_magic negotiation 
rewrite setenvif speling status unique_id userdir usertrack vhost_alias" 
CALLIGRA_FEATURES="karbon sheets words" COLLECTD_PLUGINS="df interface 
irq load memory rrdtool swap syslog" CPU_FLAGS_X86="mmx mmxext sse sse2 
aes avx avx2 f16c fma3 pclmul popcnt rdrand sha sse3 sse4_1 sse4_2 ssse3 
vpclmulqdq" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate 
evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 ntrip 
navcom oceanserver oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 
tsip tripmate tnt ublox" INPUT_DEVICES="libinput" KERNEL="linux" 
LCD_DEVICES="bayrad cfontz glk hd44780 lb216 lcdm001 mtxorb text" 
LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" 
OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php8-1" 
POSTGRES_TARGETS="postgres15" PYTHON_SINGLE_TARGET="python3_11" 
PYTHON_TARGETS="python3_11" RUBY_TARGETS="ruby31" VIDEO_CARDS="amdgpu 
radeonsi" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options 
ipp2p iface geoip fuzzy condition tarpit sysrq proto logmark ipmark 
dhcpmac delude chaos account"
Unset:  ADDR2LINE, AR, ARFLAGS, AS, ASFLAGS, CC, CCLD, CONFIG_SHELL, 
CPP, CPPFLAGS, CTARGET, CXX, CXXFILT, ELFEDIT, EMERGE_DEFAULT_OPTS, 
EXTRA_ECONF, F77FLAGS, FC, GCOV, GPROF, INSTALL_MASK, LC_ALL, LD, 
LFLAGS, LIBTOOL, LINGUAS, MAKE, MAKEFLAGS, NM, OBJCOPY, OBJDUMP, 
PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, 
PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PYTHONPATH, RANLIB, 
READELF, RUSTFLAGS, SIZE, STRINGS, STRIP, YACC, YFLAGS

=================================================================
                         Package Settings
=================================================================

media-libs/libjpeg-turbo-3.0.2::gentoo was built with the following:
USE="-java -static-libs" ABI_X86="32 (64) (-x32)"
CFLAGS="-march=raptorlake -O2 -pipe"
CXXFLAGS="-march=raptorlake -O2 -pipe"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs 
binpkg-multi-instance buildpkg-live config-protect-if-modified distlocks 
ebuild-locks fixlafiles ipc-sandbox merge-sync merge-wait 
multilib-strict network-sandbox news parallel-fetch pid-sandbox 
pkgdir-index-trusted preserve-libs protect-owned 
qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn 
unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"

Re: [gentoo-user] System crash on "Detecting C compiler ABI info"

[Paul Sopka]

On 05.04.24 08:31, Paul Sopka wrote:
> On 05.04.24 00:55, Michael wrote:
>> Your toolchain is now correct.  Can you show the output of:
>>
>> equery u media-libs/libjpeg-turbo
>>
>> and
>>
>> emerge --info media-libs/libjpeg-turbo
>>
>> However, it could be this is a bug, you can check here for reports:
>>
>> https://bugs.gentoo.org/buglist.cgi?quicksearch=media-libs%2Flibjpeg-turbo 
>>
>>
>> If this is the only package you're getting a problem with, you can run:
>>
>> emerge --resume --skipfirst
>>
>> to complete your migration to profile 23.0, then try again to emerge 
>> libjpeg-
>> turbo on its own.
Also one or two weeks ago I successfully emerged with emptytree after 
migrating to profile 23.0.

Re: [gentoo-user] System crash on "Detecting C compiler ABI info"

[Michael]

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

On Friday, 5 April 2024 07:34:01 BST Paul Sopka wrote:
> On 05.04.24 08:31, Paul Sopka wrote:
> > On 05.04.24 00:55, Michael wrote:
> >> Your toolchain is now correct.  Can you show the output of:
> >> 
> >> equery u media-libs/libjpeg-turbo
> >> 
> >> and
> >> 
> >> emerge --info media-libs/libjpeg-turbo
> >> 
> >> However, it could be this is a bug, you can check here for reports:
> >> 
> >> https://bugs.gentoo.org/buglist.cgi?quicksearch=media-libs%2Flibjpeg-turb
> >> o
> >> 
> >> 
> >> If this is the only package you're getting a problem with, you can run:
> >> 
> >> emerge --resume --skipfirst
> >> 
> >> to complete your migration to profile 23.0, then try again to emerge
> >> libjpeg-
> >> turbo on its own.
> 
> Also one or two weeks ago I successfully emerged with emptytree after
> migrating to profile 23.0.

OK, for some reason (packages which require 32bit binary compatibility, or you 
setting some specific USE flag for a package in portage) the media-libs/
libjpeg-turbo had been built also with abi_x86_32.  Now it seems your USE 
flags and corresponding build time dependencies have changed.  Can you get it 
to build with:

ABI_X86="64 -32 -x32" emerge -1aDv media-libs/libjpeg-turbo

Check what flags you have set for packages in your /etc/portage/package.use to 
make them consistent.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] System crash on "Detecting C compiler ABI info"

[Paul Sopka]

Hey Michael

Thank you for helping me. I have finally solved the issue by upgrading 
to kernel 6.8.4, see this: 
https://forums.gentoo.org/viewtopic-t-1168150.html

Have a very nice week!

Regards

Nanderty