1 |
Le dim. 5 juin 2022 à 09:49, Matthias Hanft <mh@×××××.de> a écrit : |
2 |
|
3 |
> Hi, |
4 |
> |
5 |
> I have a rather old server which I still keep alive (u never |
6 |
> know if it's needed again), so I update all packages about |
7 |
> once a month with |
8 |
> |
9 |
> emerge -aNDuv --keep-going --backtrack=999 --with-bdeps=y @world |
10 |
> |
11 |
> which works fine - until now. I can't upgrade gcc from 11.2.1 |
12 |
> to 11.3.0 because of |
13 |
> |
14 |
> make[3]: Entering directory |
15 |
> '/var/tmp/portage/sys-devel/gcc-11.3.0/work/build/gcc' |
16 |
> build/genautomata |
17 |
> /var/tmp/portage/sys-devel/gcc-11.3.0/work/gcc-11.3.0/gcc/common.md |
18 |
> /var/tmp/portage/sys-devel/gcc-11.3.0/work/gcc-11.3.0/gcc/config/i386/i386.md |
19 |
> \ |
20 |
> insn-conditions.md > tmp-automata.c |
21 |
> make[3]: *** [Makefile:2456: s-automata] Error 139 |
22 |
> make[3]: Leaving directory |
23 |
> '/var/tmp/portage/sys-devel/gcc-11.3.0/work/build/gcc' |
24 |
> make[3]: *** Waiting for unfinished jobs.... |
25 |
> |
26 |
> and dmesg says |
27 |
> |
28 |
> [ 1297.247619] genautomata[3301]: segfault at bfea1ffc ip b76bb23b sp |
29 |
> bfea2000 error 6 in genautomata[b76b1000+44000] |
30 |
> |
31 |
> Granted, it is still kernel 4.0.5, but I don't want to go through |
32 |
> the trouble of installing a new kernel on the old system. But the |
33 |
> old kernel is the only thing I can think of that could be causing |
34 |
> the problem...?! |
35 |
> |
36 |
> Possibly there was a discussion about this, in the year 2008: |
37 |
> https://gcc.gnu.org/pipermail/gcc-patches/2008-November/251389.html |
38 |
> but I don't understand what's it all about, and how could I modify |
39 |
> emerge to work around the problem. |
40 |
> |
41 |
> gcc is the only package which won't upgrade - everything else works |
42 |
> fine (including glibc 2.34-r13 and all the other stuff). |
43 |
> |
44 |
> Any hints? |
45 |
> |
46 |
> Thanks, |
47 |
> |
48 |
> -Matt |
49 |
> |
50 |
> |
51 |
> Hi Matthias |
52 |
|
53 |
It seems that the mail you found resulted in the creation of a bug in GCC |
54 |
Bugzilla, with the author of the mail also commenting on the bug. |
55 |
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38052 |
56 |
|
57 |
This bug is in status RESOLVED FIXED, so either it wasn't really fixed and |
58 |
your situation triggers it, or it's a different issue. |
59 |
|
60 |
It seems that the command line to compile "genautomata" contains useful |
61 |
information to understand the cause. |
62 |
Can you find it in the GCC compile logs ? |
63 |
|
64 |
With that you may open a bug in Gentoo or GCC Bugzilla. |
65 |
|
66 |
Best regards |
67 |
|
68 |
Mickaël Bucas |