Re: Building Soot from Subversion

[Ondrej Lhotak <olhotak@sable.mcgill.ca>]

On Sat, Jul 31, 2004 at 02:46:30AM -0400, Chris Pickett wrote:
> $ CLASSPATH= && ant
> 
> [...]
> 
> compile:
>      [javac] Compiling 2192 source files to 
> /home/research/ccl/cpicke/soot-dev/classes
> 
> BUILD FAILED
> file:/home/research/ccl/cpicke/soot-dev/build.xml:17: Error starting 
> modern compiler
> 
> -- OR --
> 
> compile:
>      [javac] Compiling 2192 source files to 
> /home/research/ccl/cpicke/soot-dev/classes
> 
>      [javac] The system is out of resources.
>      [javac] Consult the following stack trace for details.
> 
> BUILD FAILED
> Listener attempted to access System.err - infinite loop terminated

Those look like problems with your ant configuration rather than with
anything related to Soot. I am not an ant developer, but off-hand, I'd
say the first might be related to the classpath (ant can't find javac
wherever it's looking), while the second might be ant/javac running out
of heap. You can give it more heap in your .antrc:

~ $ cat .antrc 
ANT_OPTS="$ANT_OPTS -Xmx200m"

If you still can't get ant working, just compile Soot with javac without ant:

~/soot $ javac -J-Xmx200m -d classes `find {src,generated/*} -name '*.java'`

On Sat, Jul 31, 2004 at 10:24:52PM -0400, Chris Pickett wrote:
> I would humbly suggest that the active Soot developers create a "stable" 
> branch, possibly at r1503, and merge tested, stable, critical updates 
> from the trunk onto it.

As you've demonstrated, one person's critical update is another person's
useless bloat. The trunk is a consensus among a number of Soot users of
updates considered critical by some, and acceptable by the rest.

> Actually, I've gone back to using r1503, and created my own branch so I 
> can merge selected fixes if I need them.

Thank you for taking the initiative to implement your suggestion.

Ondrej