jdk16 build failure on 7.0R/i386

Scott Mitchell scott+lists.freebsd at fishballoon.org
Sat Mar 15 11:48:38 UTC 2008


On Fri, Mar 14, 2008 at 09:11:33AM -0400, Kurt Miller wrote:
> Daniel Eischen wrote:
> > 
> > I was able to get jdk16 built on 7.0.  Previously (unsuccessfully),
> > I was trying to use jdk-1.5.0.11p5,1 to build jdk16.  When that
> > didn't work, I installed jdk-1.5.0.13p7_4,1 from a package that
> > I had built on another box.  So using jdk-1.5.0.13p7_4,1, I was
> > able to build jdk-1.6.0.3p4.  I also used the same package
> > (jdk-1.5.0.13p7_4,1) to update jdk15 to the latest patchset
> > (jdk-1.5.0.14p8,1).  So now the latest patchset of both jdk15
> > and jdk16 have been built using jdk-1.5.0.13p7_4,1.  I have
> > not tried to rebuild either jdk15 or jdk16 using either of
> > the up-to-date jdks.
> > 
> > BTW, this was all done manually (cd /usr/ports/java/jdk1X;
> > make; make install).  portupgrade wanted to install compat6x
> > and diablo for no apparent reason, when there was already
> > a perfectly good native jdk installed.
> 
> Ok so you and others can build the jdks fine on 7.0R. I guess I'm out of
> ideas as to why Scott and Nicolas's systems don't record the dependency
> on libthr.so.

Yep, it's a mystery for sure... based on what Daniel's saying though, it
might be worth me trying to build the latest jdk-1.5.0 and bootstrapping
from that instead of diablo.

Thanks all for your help with this.

	Scott

-- 
===========================================================================
Scott Mitchell           | PGP Key ID | "Eagles may soar, but weasels
Cambridge, England       | 0x54B171B9 |  don't get sucked into jet engines"
scott at fishballoon.org | 0xAA775B8B |      -- Anon


More information about the freebsd-java mailing list