Date: Fri, 22 Jul 2005 13:47:27 +0100 (BST) From: Jan Grant <Jan.Grant@bristol.ac.uk> To: Panagiotis Astithas <past@ebs.gr> Cc: Frank Staals <f.staals@zonnet.nl>, Ralf Folkerts <ralf.folkerts@gmx.de>, freebsd-java@freebsd.org Subject: Re: Eclipse 3.1 port? Message-ID: <Pine.GSO.4.62.0507221345550.8597@mail.ilrt.bris.ac.uk> In-Reply-To: <42E0B533.2060306@ebs.gr> References: <1120942860.19352.7.camel@localhost.eu.mscsoftware.com> <42D99A15.7090408@ebs.gr> <42DEBF05.9050103@ebs.gr> <1121975583.994.14.camel@beaster> <42E000B5.6050903@zonnet.nl> <42E0B533.2060306@ebs.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 22 Jul 2005, Panagiotis Astithas wrote: > Weird, I have never seen the src error myself. Could both of you send me > privately (or put somewhere and send me a link to) the full output of a build > up to that point? Something like: > > make clean build |& tee /var/tmp/eclipse.log > > I'll see if I can reproduce it this weekend. No need to worry about the javac > warnings, though. I saw this too, but only when I'd made a copy of java/eclipse-devel somewhere outside the ports tree, patched it, and run from there. Once I patched the "real" port, it apepared to work correctly. Having said that, there was no apparentl reason I could discern that the build should have failed. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44 (0)117 9287088 or 3317661 http://ioctl.org/jan/ Solution: (n) a watered-down version of something neat.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.62.0507221345550.8597>