[04:13] <rom1v> salut
[04:13] <rom1v> hi
[04:22] <xhaker> hi
[04:31] <man-di> xhaker: I have some strange problems with eclipse
[04:31] <man-di> it mostly hangs on the eclipse.linux.tar target
[04:31] <man-di> it works on 1/100 builds
[04:35] <xhaker> man-di, hmm, the build hangs?
[04:36] <man-di> yes
[04:36] <xhaker> gcj 4.2 :/
[04:37] <xhaker> if you don't build natives it goes fine
[04:37] <man-di> I have seen this on a pure i386 machine too, some time ago, but it was away after reboot
[04:37] <man-di> this is gcj 4.1
[04:37] <xhaker> i'm building in a pentium-m
[04:38] <man-di> I'm building now on Core2Quad
[04:38] <xhaker> i noticed the build taking too much memory, <10% cpu, on the natives building part
[04:39] <man-di> it has plenty of ram too
[04:39] <xhaker> man-di, my build with natives lasted more than 12h until i decided to kill it.. 
[04:40] <xhaker> It would probably finish, because i've seen it take long at every jar but still go through
[04:40] <man-di> when it worked once here, it finished after 40 minutes
[04:41] <man-di> and I saw some new lintian warnings
[04:41] <man-di> so i fixed them
[04:41] <xhaker> man-di, you must be kidding, 12h+ here with natives enabled :/
[04:41] <man-di> then I wanted to rebuild, but it hangs each time
[04:41] <man-di> 40 minutes here with natives enabled, for real
[04:42] <xhaker> man-di, spawn top or saidar during the build
[04:42] <man-di> during java compilation mostly one processor is used
[04:42] <man-di> but when building to native all processors are used 100%
[04:42] <man-di> I tested this
[04:43] <xhaker> maybe saidar, so you can see the disk trashing
[04:43] <xhaker> man-di, during the long build
[04:43] <man-di> never used saidar
[04:43] <xhaker> i seemed to have accelerated the build with synctl -w vm.swappiness=10
[04:44] <xhaker> man-di, from my point of view gcj was using huge amounts of memory and swap, and lots of disk trashing
[04:44] <man-di> it does use much memory
[04:44] <man-di> thats a known issue
[04:45] <xhaker> man-di, saidar is cool, install it.. you just need to run it in a terminal, it shows cpu stats, memory, network, disk bw
[04:45] <man-di> Eclipse uses 2 GB of my ram during native compilation
[04:46] <xhaker> man-di, i'd guess the 40min build was on a system where the memory free was just right
[04:46] <xhaker> man-di, imagine me building it on this 512mb laptop
[04:46] <xhaker> kinda wierd looking at the cpu running 1.3% and the memory all taken out
[04:48] <man-di> xhaker: yes it was on my Quad2Core
[04:48] <man-di> 4x2.4 Ghz
[04:48] <xhaker> man-di, in the rules file there is some magic dealing with memory near the top
[04:48] <man-di> and 2 GB ram
[04:49] <xhaker> do you happen to know abou it?
[04:49] <man-di> I need to upgrade ram a bit, I think
[04:50] <man-di> thats only calculating the number of cpus for the bytecode2native compilation
[04:51] <man-di> to not use too much cpus on systems with much cpus but not much memory
[04:59] <xhaker> man-di, the disk trashing on the eclipse build lead me to try to fix the kernel support for this laptop.. i was running udma2 now udma5
[04:59] <xhaker> not all is bad
[05:00] <man-di> at least you had a goof reason to fix it