El Fri, Jul 01, 2005 at 01:25:45AM -0400, Jason Castonguay me dec?a:
> Hi Fernando.
>
> Thanks for responding. I can't say that I CHECKED my hardware because I
> thought that it might be referring to the lack of memory as being the
> actual problem.
I see your other post when you say the error is completely reproducible, so
maybe RAM has nothing to do with it, nevertheless i'm talking from the
experience: for hours and hours i tried everything i can think of, and
everything i can found in the internet. When i finally discover RAM was buggy
and changed it everything go smooth. So i think is not bad idea to try it, just
in case ;)
> So I went out and bought some brand new Centon DIMMs.
> The computer sees them fine, but perhaps I should test them.
I really encourage this.
Before getting gentoo on this machine (Athlon 3000+) i tried gentoo on a K6-2
500 Mhz with 256 MB of RAM, and i really suffer the time needed to get something
up. Besides i have a couple of problems and after three tries in a week i give
up.
> I do know
> that, as the compilation is going on, I can see the memory running out as
> I continue to monitor. It ends up using all of it for some strange reason
> (all 512MB just about). The same thing was happening with my 128MB,
> though I think things were quitting much sooner. Now, it'll chuug away at
> glibc for about 3.5 hours or so. Before, it was just an hour or less.
> Very strange.
Hum... I cloudly remember that there was an issue with "-pipe" in CFLAGS in my
first attempts to install gentoo. Maybe "-pipe" is eating your memory?
Here is my CFLAGS="-O2 -march=athlon-xp", very conservative, no optimizations.
But this is something a never confirmed, so take this "removing -pipe" stuff
with a bit (lot?) of sorcery ;)
--
Bart: What religion are you?
Homer: You know, the one with all the well-meaning rules that don't
work out in real life, uh, Christianity.
Homerpalooza
--
gentoo-user@gentoo.org mailing list
