From: Peter D. <pe...@re...> - 2007-05-10 20:21:46
|
On 5/8/07, Andrew John Hughes <an...@dc...> wrote: > As to using this in future, I notice that the build pulls down ecj (although > ant stubbornly refused to use my copy). If you configure the setup properly (namely creating the appropriate properties in ${components.dir}/components.properties then this should not be the case. IIRC you need to add a ecj.dir and setup that dir in way we expect. Of course I am not sure any of this is documented ;) > Is there a reason it ignores the > user's compiler and uses the downloaded ecj to compile Classpath? Classpath 0.93 does not compile with javac, nor does it compile with jikes and thus has to use ecj. It will use any ecj as long as you have configured it correctly. > Maybe it > would be possible to instead download openjdk which supports the annotation > stuff? Possibly. Are you volunteering to look into it? :) > Speaking of which, I got a strange error when downloading Classpath. The get > process seems to have decided to ungzip the file itself, causing the later > tar invocation to fail. I altered the build file for the time being, but > this seems very odd. That does not seem like desired behavior. Sounds like a bug either in your java runtime or http proxy. > I also note from its build file that it can instead > drag in a CVS copy, but this doesn't seem to be documented in the user guide. I have not tried it for a long time so I am not sure it still works ;) > At the moment, I'm stuck (and not yet having reached the boot image!) because > I stupidly updated and the build now seems to have broken. Is anyone else > getting: As Ian indicated "ant real-clean" should do the trick. -- Cheers, Peter Donald |