jdk16 build failure on 7.0R/i386

[Scott Mitchell]

On Sat, Mar 15, 2008 at 11:22:07PM +0000, Scott Mitchell wrote:
> On Sat, Mar 15, 2008 at 11:48:32AM +0000, Scott Mitchell wrote:
> > 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.
> 
> Well, that failed in the same way as the jdk16 build.  I'm starting to
> think there's maybe something not configured right on this machine,
> although it's not had any trouble building anything else since I upgraded
> it to 7.0 (binary upgrade using freebsd-update).  I'm going to try a source
> upgrade to 7.0 on another box and see if I have any more luck there.

Success at last!  Finally managed to build jdk16 (bootstrapped from the
latest diablo 1.5 package for FreeBSD 6) on a machine source-upgraded from
RELENG_6 to RELENG_7.  I'm wondering if there's some stray old bit of 6.3
still hanging around on the binary-upgraded 7.0 machine that was having all
the problems...?

Anyway, it's working now and I have the package safely hidden away in case
I need it elsewhere.  Thanks again to everyone who helped with this, I'll
be sure to post again if I figure what exactly what is weird about the
machine I can't do the build on.

Cheers,

	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