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
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
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:
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:
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
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:
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:
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
> >
> >
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
: "Paul Sopka"
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
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
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
> >>
> >> ?
> >
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
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
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
14 matches
Mail list logo