Le dim. 5 juin 2022 à 09:49, Matthias Hanft a écrit :
> Hi,
>
> I have a rather old server which I still keep alive (u never
> know if it's needed again), so I update all packages about
> once a month with
>
> emerge -aNDuv --keep-going --backtrack=999 --with-bdeps=y @world
>
> which works fine - until now. I can't upgrade gcc from 11.2.1
> to 11.3.0 because of
>
> make[3]: Entering directory
> '/var/tmp/portage/sys-devel/gcc-11.3.0/work/build/gcc'
> build/genautomata
> /var/tmp/portage/sys-devel/gcc-11.3.0/work/gcc-11.3.0/gcc/common.md
> /var/tmp/portage/sys-devel/gcc-11.3.0/work/gcc-11.3.0/gcc/config/i386/i386.md
> \
> insn-conditions.md > tmp-automata.c
> make[3]: *** [Makefile:2456: s-automata] Error 139
> make[3]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-11.3.0/work/build/gcc'
> make[3]: *** Waiting for unfinished jobs
>
> and dmesg says
>
> [ 1297.247619] genautomata[3301]: segfault at bfea1ffc ip b76bb23b sp
> bfea2000 error 6 in genautomata[b76b1000+44000]
>
> Granted, it is still kernel 4.0.5, but I don't want to go through
> the trouble of installing a new kernel on the old system. But the
> old kernel is the only thing I can think of that could be causing
> the problem...?!
>
> Possibly there was a discussion about this, in the year 2008:
> https://gcc.gnu.org/pipermail/gcc-patches/2008-November/251389.html
> but I don't understand what's it all about, and how could I modify
> emerge to work around the problem.
>
> gcc is the only package which won't upgrade - everything else works
> fine (including glibc 2.34-r13 and all the other stuff).
>
> Any hints?
>
> Thanks,
>
> -Matt
>
>
> Hi Matthias
It seems that the mail you found resulted in the creation of a bug in GCC
Bugzilla, with the author of the mail also commenting on the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38052
This bug is in status RESOLVED FIXED, so either it wasn't really fixed and
your situation triggers it, or it's a different issue.
It seems that the command line to compile "genautomata" contains useful
information to understand the cause.
Can you find it in the GCC compile logs ?
With that you may open a bug in Gentoo or GCC Bugzilla.
Best regards
Mickaël Bucas
