Re: [jnc-users] JNC hangs

[Lee D. P. <le...@3s...>]

> >
> > 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
>=20
> 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?
>=20

This is a Windows XP Service Pack 2 machine with 1 GB memory.=20

All of the jar files are compiled as a whole except swt.jar which is
references only.=20

> > 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;
>=20
> Would be nice to know the result with optimization.
> >
> > 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.
>=20
> 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.
>

I've now run a few more builds and have a bit more information. I can
successfully compile SWT if I compile the whole jar but of course this
has linking issues with AWT. This produces the following output in the
log.

     [exec] - processing swt-win32.jar
     [exec] [gcc-121694-win\bin\gcj
     [exec] -fjni
     [exec] -O2
     [exec] -Ilibs/win/gui/gui.jar
     [exec] -c
     [exec] ..\..\sslexplorer-agent\build\extension\swt-win32.jar
     [exec] -o
     [exec]
C:\DOCUME~1\lee\LOCALS~1\Temp\JNCTemp2ogdqu.out\swt-win32-win.jar.o
     [exec] -I..\..\sslexplorer-agent\build\extension\nanoxml-2.2.3.jar
     [exec] -I..\..\sslexplorer-agent\build\extension\agent-debug.jar
     [exec]
-I..\..\sslexplorer-agent\build\extension\maverick-ssl-debug.jar
     [exec]
-I..\..\sslexplorer-agent\build\extension\maverick-crypto.jar
     [exec] -I..\..\sslexplorer-agent\build\extension\agent-en.jar
     [exec] -I..\..\sslexplorer-agent\build\extension\agent-swt-en.jar
     [exec] -I..\..\sslexplorer-agent\build\extension\log4j-java1.1.jar
     [exec]
-I..\..\sslexplorer-agent\build\extension\commons-logging-java1.1.jar
     [exec]
-I..\..\sslexplorer-agent\build\extension\maverick-util-debug.jar
     [exec] -I..\..\sslexplorer-agent\build\extension\jRegistryKey.jar
     [exec] -I..\..\sslexplorer-agent\build\extension\jzlib.jar
     [exec]
-I..\..\sslexplorer-agent\build\extension\agent-swt-debug.jar]

The problem seems to be when I have the swt.jar set to references only.
When I have this option, with or without optimization I only get the
following output in the log.

     [exec] - processing swt-win32.jar

I'm not sure if that's a clue but I never see the command output as the
successful compile above shows. This is using the same .jnc file with
the only difference being that the jar flag is unset to include
referenced classes only.

Memory usage seems to be within the available limits. I'll try
increasing the virtual memory to see if that makes a difference.=20

Thanks,

Lee