Date: Sun, 31 Oct 2010 17:05:38 +0100 From: Thomas Gellekum <Thomas.Gellekum@gmx.de> To: Michael Martin <mgmartin@comcast.net> Cc: freebsd-eclipse@freebsd.org Subject: Re: Upgrade eclipse-devel to 3.6.1 Message-ID: <86pquq8i0d.fsf@siegel.tg.intern> In-Reply-To: <4CCD81A5.6090207@comcast.net> (Michael Martin's message of "Sun, 31 Oct 2010 08:48:05 -0600") References: <86ocaepvsy.fsf@siegel.tg.intern> <4CC97027.9050805@comcast.net> <86zktxazsg.fsf@siegel.tg.intern> <20101031.233825.1348995565861218514.ken@tydfam.jp> <4CCD81A5.6090207@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Martin <mgmartin@comcast.net> writes: > On 10/31/10 08:38, ken wrote: > > Thomas, > 20101029-Patch went well and compiled successfully on FreeBSD-current(amd64). It starts and goes to banner, but it dies before having screen. > Something goes wrong with -current + gnome2. > > > I'm running 9.0-CURRENT too, amd64 and mine was ok. That's great to hear. I did actually have two changes in the latest patchset, but only expected to fix the SWT issue. > Did you try with an > empty ~/.eclipse folder? Also try an empty ~/workspace folder. I also > had to point to openjdk ( using setenv JAVA_HOME ) -- diablo sigsegv'd on > me. Looks like /usr/local/bin/eclipse-devel defaults to openjdk, so check > that your JAVA_HOME is not pointing to diablo or somewhere else, as this > will over-ride the eclipse-devel script default. This, however, is worse than I thought. On i386, diablo-jdk16 can run the resulting eclipse, it "only" crashes while building eclipse. Maybe we need to hardcode the Java version in the startup script. Users can still configure the JRE used by JDT/PDE through the preferences. tg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86pquq8i0d.fsf>