Le dim. 5 juin 2022 à 09:49, Matthias Hanft <
mh@hanft.de> 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
<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le dim. 5 juin 2022 à 09:49, Matthias Hanft <<a href="mailto:
mh@hanft.de" target="_blank">
mh@hanft.de</a>> a écrit :<br></div><blockquote
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
I have a rather old server which I still keep alive (u never<br>
know if it's needed again), so I update all packages about<br>
once a month with<br>
emerge -aNDuv --keep-going --backtrack=999 --with-bdeps=y @world<br>
which works fine - until now. I can't upgrade gcc from 11.2.1<br>
to 11.3.0 because of<br>
make[3]: Entering directory '/var/tmp/portage/sys-devel/gcc-11.3.0/work/build/gcc'<br>
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 \<br>
insn-conditions.md > tmp-automata.c<br>
make[3]: *** [Makefile:2456: s-automata] Error 139<br>
make[3]: Leaving directory '/var/tmp/portage/sys-devel/gcc-11.3.0/work/build/gcc'<br>
make[3]: *** Waiting for unfinished jobs....<br>
and dmesg says<br>
[ 1297.247619] genautomata[3301]: segfault at bfea1ffc ip b76bb23b sp bfea2000 error 6 in genautomata[b76b1000+44000]<br>
Granted, it is still kernel 4.0.5, but I don't want to go through<br>
the trouble of installing a new kernel on the old system. But the<br>
old kernel is the only thing I can think of that could be causing<br>
the problem...?!<br>
Possibly there was a discussion about this, in the year 2008:<br>
<a href="
https://gcc.gnu.org/pipermail/gcc-patches/2008-November/251389.html" rel="noreferrer" target="_blank">
https://gcc.gnu.org/pipermail/gcc-patches/2008-November/251389.html</a><br>
but I don't understand what's it all about, and how could I modify<br> emerge to work around the problem.<br>
gcc is the only package which won't upgrade - everything else works<br> fine (including glibc 2.34-r13 and all the other stuff).<br>
Any hints?<br>
Thanks,<br>
-Matt<br>
<br></blockquote><div><div>Hi Matthias</div><div><br></div><div>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.<br></div><div><a href="
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38052">https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38052</a></div><div><br></div><div>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.</div><div><br></div><div>It seems that the command line to compile "genautomata" contains useful information to understand the cause.</div><div>Can you find it in the GCC compile logs ?<
/div><div><br></div><div>With that you may open a bug in Gentoo or GCC Bugzilla.</div><div><br></div><div>Best regards<br></div><div><br></div>Mickaël Bucas<br> </div></div>
</div>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)