aMule Forum
English => aMule Help => Topic started by: catface on December 23, 2003, 08:22:33 AM
-
if compiling a code will crash XFree, you surely have something wrong with your system
-
muuli_wdr.cpp is a 1.9Mb file. Thus, compilation takes lots of memory and CPU, and gcc sometimes can't handle that. It's gcc problem, not amule ;)
Try compiling on text console, without X
-
yeah, this sounds like the "out of memory killer" (OOM killer) in the kernel which tries to free memory by killing processes if a running process runs out of free memory.
i had the same problems with the same file.
like Kry said, switch to text console and terminate all unnecessary processes. increasing swap space might help, too.
and btw: afaik the OOM killer only applies if you compile as superuser (root). switch to any ordinary user to compile and no processes should be killed (though compiling might still fail).
fz
p.s.: to the devs: any way to reduce the size of muuli_wdr?
-
Original von fz
p.s.: to the devs: any way to reduce the size of muuli_wdr?
its the GUI ..
-
i know. perhaps there's a way to produce smaller source code in exchange for "human readability"? i don't know wxgtk, but i noticed an increase in file size beginning with amule 1.2.0 (which i couldn't compile, too, because of the too large file size), though i didn't notice large changes in the gui.
greets, fz
-
hmm... can anyone tell me how much of a memory/CPU the compilation of aMule takes?
I know that I'm not really up-to-date with my Celeron 500.. but I've always expirienced Linux as the System, that really runs everywhere...
Maybe I should go back to xMule again :?
-
Well, muuli_wdr is generated, so, no way to reduce it.
About OOM: sorry, jMCg, but some low-end boxes (as my p2 266 128Mb RAM) can handle the compilation (it takes ages anyway!!). Try changing gcc version, 'cos its a segmentation fault, not a killed, and it happens under user, not root, compilation.