Sounds like a memory problem. It may have worked compiling for 4 straight days, but did you attempt to use it interactively at all during that time? Does the hard drive churn while compiling gcc?
I did the whole install via ssh but other than that, no interactivity. They are pretty old hard drives and it seems I can hear em churning when its doing any disk activity.
The best you can do is leave it until it is done or compile it on another box with emerge's -b option.
I was thinking that, but wanted to do that as a last resort, because obviously I am going to need to find a solution at some point.. better now than later.
After posting the first time, I remembered that I recompiled the kernel (gentoo-sources) a couple weeks ago.. All I changed in the config were some grsecurity settings. Do you think that could have anything to do with it?
Thanks again, Aaron
-- [EMAIL PROTECTED] mailing list
