Re: [jnc-users] JNC hangs
Status: Beta
Brought to you by:
soapy
From: Marco T. <mt...@gm...> - 2007-02-19 07:15:06
|
Lee D. Painter wrote: >>> If I attempt to compile the same project with 1.1 it hangs when >>> processing the swt.jar. >> This is a whole new topic. What do you mean by hang? >> Is there an output? How long did you wait? Did you try without >> optimization? > > The compile never completed. The JNC window just stayed with the text > below (I had set the flag to output commands btw and these were not > output) > > : processing swt-win32.jar You might run out of RAM/Swap. GCJ 4.3 needs a lot more compared to GCJ 4.2. I can compile swt without problems. What operating system do you have? How much Ram? How do you compile the jar? The whole or only needed references? > I started the build just as I was leaving for the office yesterday > morning and it was still at that point 8 hours later. I didn't try > without optimization; Would be nice to know the result with optimization. > I tried a few more builds directly with auto > compiler with the same results AutoCompiler actually only executes "JavaNativeCompiler -compile theFile.jnc" while keeping the console open. So, not really surprising :-) > last night so decided to leave it at that > and continue testing with 1.0.1 which continued to build within 10-15 > mins. If I get time I'll upgrade again and try some different options to > see if I can isolate the problem. > >>> There is no trace of any gcj or related >>> processes in task manager when this happens. >> I think cc1.exe or jc1.exe should be in the process list. Just look > for >> the process consuming the most memory or/and cpu. > > There were no processes running except the JavaNativeCompiler.exe. > Normally when compiling I see quite a bit of activity in the task > manager with jc1, gcj, ar or cc1. Very strange! The GUI frontend calls "gcj" and waits until it returns. So there really ought to be something... Unless you run out of memory of course. Then the behavior is unspecified I guess. Marco |