Date: Wed, 8 Aug 2007 15:01:31 +1000 From: "Justen Stepka" <jstepka@jstepka.name> To: "Jonathan Chen" <jonc@chen.org.nz> Cc: freebsd-java@freebsd.org Subject: Re: 6.2-STABLE JDK 1.5 compilation errors Message-ID: <c80586cc0708072201v2c147f78r2d20e4cdd7df60c1@mail.gmail.com> In-Reply-To: <20070807102734.GA87862@osiris.chen.org.nz> References: <c80586cc0708070214h1f8dd9a6xca861ca764f3e285@mail.gmail.com> <20070807100340.GB86955@osiris.chen.org.nz> <c80586cc0708070320n193e271fi7e274475abff0e44@mail.gmail.com> <20070807102734.GA87862@osiris.chen.org.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/7/07, Jonathan Chen <jonc@chen.org.nz> wrote: > On Tue, Aug 07, 2007 at 08:20:47PM +1000, Justen Stepka wrote: > > On 8/7/07, Jonathan Chen <jonc@chen.org.nz> wrote: > > > On Tue, Aug 07, 2007 at 07:14:07PM +1000, Justen Stepka wrote: > > > > It's been a while since I've compiled the JDK -- but it's good to see > > > > things are still the same :). > > > > > > > > Today I ran into some compiling errors with the 1.5 JDK on 6.2-STABLE > > > > (as of this morning). > > > > > > > > Here are the compilation errors: > > > > > > > > /usr/ports/java/jdk15/work/control/build/bsd-i586/gensrc/sun/nio/cs/StandardCharsets.java:226: > > > > <identifier> expected > > > > Java HotSpot(TM) Client VM warning: Can't detect initial thread stack > > > > location - find_vma failed > > > [...] > > > > > > What's your bootstrap JDK? > > > -- > > > Jonathan Chen <jonc@chen.org.nz> > > > ----------------------------------------------------------------------- > > > "I love deadlines. I like the whooshing sound they make as they fly by" > > > - Douglas Adams > > > > > > > linux-sun-jdk-1.5.0.12,2 > > Did you remember to mount the linux procfs? Alternatively, you can use > the diablo-native jdk to bootstrap. > > Cheers. > -- > Jonathan Chen <jonc@chen.org.nz> > ---------------------------------------------------------------------- > Do not take life too seriously. > You will never get out of it alive. > Sure enough that turned out to be the issue. Not sure why, but running these commands: kldload linprocfs mount -t linprocfs linprocfs /compat/linux/proc still resulted in the same error until I did a 'make clean' and then 'make ; make install'. -- Justen Stepka http://www.jstepka.name/blog/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c80586cc0708072201v2c147f78r2d20e4cdd7df60c1>