On 9/3/24 19:39, Dale wrote:
Grant Edwards wrote:
On 2024-09-03, Dale <rdalek1...@gmail.com> wrote:
I was trying to re-emerge some packages. The ones I was working on
failed with "internal compiler error: Segmentation fault" or similar
being the common reason for failing.
In my experience, that usually means failing RAM. I'd try running
memtest86 for a day or two.
--
Grant
I've seen that before too. I'm hoping not. I may shutdown my rig,
remove and reinstall the memory and then test it for a bit. May be a
bad connection. It has worked well for the past couple months tho.
Still, it is possible to either be a bad connection or just going bad.
Dang those memory sticks ain't cheap. o_~
Thanks. See if anyone else has any other ideas.
Dale
:-) :-)
Please refresh my memory, what brand of CPU ( Intel or AMD ) is in your
new rig?
----
If AMD, binutils can build -broken- without failing the compile process.
gcc starts segfaulting constantly.
workaround :
setup a package.env for gcc and binutils.
gcc.conf contents :
CFLAGS="-march=generic -O2 -pipe"
CXXFLAGS="-march=generic -O2 -pipe"
use the old version of gcc to rebuild both binutils and gcc ( the new
version ).
leave this fix in place, and prevent this error from reoccurring.
Hope this helps,
Corbin
