Richard Fish wrote:
On 12/5/05, b.n. <[EMAIL PROTECTED]> wrote:
In fact, I have -O3 and -j2 ...And I didn't imagine that compiling xmame
could take so much memory. But I already compiled xmame in the past, and
I had no serious problems. Do you think that adding the "joystick" USE
flag made it all growing just too big?
Maybe, but I doubt it. More likely something else in your environment
is different. We know that you were running firefox during the
compile, and the memory usage there depends heavily upon what web
pages you had open and the size of the in-memory cache you have
enabled.
I also had several other programs open (3 bittornado instances, amule,
konqueror etc.)...although on fluxbox...
But I never had problems even with huge compiles like OO.org or KDE.
Oh, well, there's a first time for everything, I guess. :)
It could even be a difference in gcc versions: I think recent versions
of gcc consume more memory for -O3 (due to more optimizations being
enabled) than previous versions.
I'm still on GCC 3.3 ...and now I'm less and less prone to step forward
to 3.4 (I don't want my system to crash during an emerge -e world).
m.
--
[email protected] mailing list
