Joseph wrote:
[snip]
I wasn't thinking about masking KDE but gcc-3.4.1 on AMD64 platform and
make stable 3.3 version. I run onto one posting claiming that there is
some kind of bug in gcc-3.4.1 (and this version is the only stable
version on AMD64.
If I knew I'm going to have so much problem with AMD64, I would have
gone with x86.
So WARNING to everybody: A8V + Sata Drive + AMD64 3000 = DISASTER (for
now).
I have two other boxes running Gentoo on x86 and they are rock solid.
If any kind of problem pops-up I can solve it withing an hour or faster.
But these two problem on AMD64 turned this machine to a piece of junk
(suitable only for Windows).
Split KDE-ebuild is effected as well.
I couldn't find anything in dmesg, what might be causing it. If it was
a kernel configuration I would imaging somebody would discover it, but
there are only suggestion that don't work. It most likely some bug in
some kind of kernel driver pertaining to Sata Drive or AMD64
Maybe you should try gcc-3.4.4? You could go with a 32-bit userland
until the problem is resolved. You can do that with a 64-bit kernel
if you have IA32 emulation enabled (hopefully you won't encounter the
same bug).
Zac
Thank you, that is a good suggestion.
I'll be running memtest86 all night, just to be sure.
And tomorrow I'll try gcc-3.4.4 it this will not help I'll try IA32
emulation. Though, I'll have to find some more info in this, how to do
it.
It's easy, just enable it in your kernel config. You can use 32-bit
module-init-tools to modprobe 64-bit modules. You need a 64-bit environment to
build 64-bit stuff but you can chroot into a stage3 for that. Read the amd64
technotes part about 32-bit compatibility:
http://www.gentoo.org/proj/en/base/amd64/technotes/index.xml?part=1&chap=4
BTW, gcc-3.4.1 is no longer stable on amd64 but gcc-3.4.3-r1 is:
http://packages.gentoo.org/packages/?category=sys-devel;name=gcc
Zac
--
gentoo-user@gentoo.org mailing list
