------- Comment #3 from paolo dot bonzini at lu dot unisi dot ch 2006-09-21 08:21 ------- Subject: Re: [ecj] update build instructions to account for changes
> This is found using the normal gcc specs approach. In a distribution > I'd expect ecj1 to end up in the gcc-lib dir. In my case I just have > it on my PATH. > > We won't be including the ecj sources in the gcc tree. As I recall that > was rejected by the SC. So it will always be a separate download. > The best thing would be if I could just "sudo apt-get install ecj". If there are any differences between ecj and ecj1, we should provide some kind of wrapper. A nice possibility, would be to support dropping the downloaded JAR somewhere in the tree where it installs correctly and automagically. This would not be against the SC decision. > Both ecj and the new gcjh can be run on any vm, including all the free > ones. I've built libgcj many times running these purely interpreted > and it is not painfully slow. Cool, though not unexpected because the code generation of Java bytecodes is not that hard (apart from the unreachable and uninitialized code checking). Paolo -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28938