Why is that every single time I try to compile a kernel the compiler
Sometimes gcc (the one that comes with slackware 3.0) quits with a message
about virtual memory being exhausted, even though I have 32 megs of memory
and 32 megs of swap. If I restart compiling by typing "make" again, it
usually continues from where it left off. That is perhaps somehow
understandable (?) However, the compiler blows up all the time on other
things... missing files, symbol problems, gcc just quiting-- weird
problems that I can't reproduce.
To fully compile a kernel, I have to restart make over and over again!
Sometimes I have to do a make mrproper, make depend, make clean.
Sometimes I have to reboot in between... or I'll login and out several
This happens with several different kernel sources (1.2.13 patched for ELF
at the moment), and different Slackwares. Does anyone know what the heck
is going on???
I've never mentioned this before. Because I thought, maybe this is just
MY weird computer, even though I have very run of the mill stuff (486/66,
Buslogic SCSI, SB16, Mach64 video card). But recently I was over at a
friend's house watching him install Linux on his machine. He was using
Slackware 2.2, and he had totally different hardware, yet he had the exact
So is this normal? Does EVERYONE installing Linux have this problem? Is
this just the way it is with Linux? I don't like these kinds of problems.
The reason I run Linux is becuase I want UNIX, but moreover I NEED
preemptive multitasking, protected memory, and stability. I want to be
able to start X-Windows (something I don't dare do while compiling a
kernel right now), and compile a new kernel in the background. Is that so
If anyone knows why these bad things are happening, would you please
PLEASE tell me? It scares me! I have become really dependent upon Linux,
and I will do anything to fix this problem.