porting icedtea6 to FreeBSD

Thu Mar 29 02:36:14 PDT 2012

----- Original Message -----
> Hi,
> On Wed, Mar 28, 2012 at 06:09:22PM -0400, Andrew Hughes thus spake:
> >> >It's hard to tell what's happening here without more details as
> >> >to
> >> >how
> >> >you're building.  Posting config.log would be very helpful.
> >>
> >> I've attached this.
> >>
> >
> >Ok, seems sane enough.  I do wonder what /usr/local/openjdk6 is
> >though.
> >That may cause problems further down the line.
> 
> This is my installation of OpenJDK6. It has been ported to FreeBSD
> for
> sometime now. Do I need to specify a different jdk for building?
> 

So what's the basis for that?  Wouldn't it be better to use that source
code rather than OpenJDK6?

> I am specifying this for --with-jdk-home
> >
> >You don't seem to be using the latest; that would be 1.11.1.  If you
> >want
> >to get the end result into IcedTea, you may be better working with
> >the
> >Mercurial version:
> 
> I really would rather work with the released tarballs to support
> FreeBSD,
> unless something comes up where that can't be done. I'm really not
> convinced
> that I'm doing things right at this point to warrant a different path
> :)
> 

There just doesn't seem much point in working on an old release with issues
that may have already been fixed.  Also, to accept any patches you may have,
we'll need them against HEAD not an old release.

> I'm still trying to find out what icedtea does with openjdk :)

Patches and builds it.

> >
> >The patch issue is rather odd.  Are you rerunning a build over an
> >existing
> >OpenJDK tree as Andrew said?  What I'd recommend for ease of
> >debugging is
> >to build in a separate directory:
> 
> I believe I am doing that, with the above specified. Do I need to be
> running
> against a different jdk home? There are several to choose from for
> FreeBSD.
> I wonder if this is the issue. However, I switched to use jdk1.6 and
> had the
> same patch related issue.

The JDK isn't an issue with patching.  I just mentioned it because it may
affect things when we actually get to building.

> 
> The text leading up to this was:
> --------------------------
> |# HG changeset patch
> |# User robm
> |# Date 1322691030 0
> |# Node ID ee0f12b18cb8d20c3fb61e96817bde6318a29221
> |# Parent  dd8956e41b892ed7102e1d5668781f2c68ea9ac5
> |7082299: AtomicReferenceArray should ensure that array is Object[]
> |Summary: java.util.concurrent.AtomicReferenceArray needs to ensure
> |that internal array is always Object[].
> |Reviewed-by: chegar, coffeys
> |
> |diff --git
> |a/src/share/classes/java/util/concurrent/atomic/AtomicReferenceArray.java
> |b/src/share/classes/java/util/concurrent/atomic/AtomicReferenceArray.java
> |---
> |openjdk/jdk/src/share/classes/java/util/concurrent/atomic/AtomicReferenceArray.java
> |+++
> |openjdk/jdk/src/share/classes/java/util/concurrent/atomic/AtomicReferenceArray.java
> --------------------------
> Patching file
> openjdk/jdk/src/share/classes/java/util/concurrent/atomic/AtomicReferenceArray.java
> using Plan A...
> Reversed (or previously applied) patch detected!  Assume -R? [y]
> 
> >
> >$ mkdir icedtea6-build
> >$ cd icedtea6-build
> >$ ../icedtea6-1.11.1/configure <params>
> 
> This may partly my issue. I'm basically guessing what the correct
> options
> are to use.
> 
> Here is what I am using currently:
> (LOCALBASE=/usr/local)
> 
> --with-ecj-jar=${LOCALBASE}/share/java/classes/ecj-3.7.2.jar \
> --with-rhino=${LOCALBASE}/share/java/rhino/rhino.jar \
> --with-jdk-home=/usr/local/openjdk6 \
> --with-jaxp-drop-zip=${DISTDIR}/jaxp144_03.zip \
> --with-jaf-drop-zip=${DISTDIR}/jdk6-jaf-b20.zip \
> --with-jaxws-drop-zip=${DISTDIR}/jdk6-jaxws2_1_6-2011_06_13.zip \
> --with-openjdk-src-zip=${DISTDIR}/openjdk-6-src-b24-14_nov_2011.tar.gz

Yes I saw this.  All looks fine to me.

Moving to 1.11 would allow the xerces/xalan dependencies to be dropped
(this change will also be in 1.10.7)

> 
> >which you can then just rm -rf if it doesn't work.  make clean works
> >too,
> >but this is usually quicker and more guaranteed to work.
> >
> >You mention something about having to fix up patches?  Can you give
> >more
> >details?
> 
> This has been resolved with later releases, and the patching is
> probably a
> result of misconfigured configured options.

I doubt it from what I've seen of what you're doing.

The issue seems to be that your OpenJDK sources are not in the expected state.

> >
> >> Please take note the files and locations where they are being
> >> downloaded from.
> >> >
> >> >http://icedtea.classpath.org/hg/icedtea6-hg
> >> >
> >> >Going forward, I doubt this will work as OpenJDK6 doesn't have
> >> >the
> >> >*BSD work
> >> >that Oracle have integrated for Mac OS X.  You might be better
> >> >starting from
> >> >7.  6 is likely to end up having to be retired by the end of the
> >> >year anyway,
> >> >as Oracle intend to stop security support.
> >>
> >> If I can get this to work on 6 it would be great, however I can
> >> work
> >> on 7 as
> >> well. Is there anything I can not apply to get it to work on 6?
> >>
> >
> >You're more than welcome to try and don't get me wrong - I love to
> >see
> >FreeBSD support for OpenJDK6. I just worry that it'll be a lot of
> >work
> >for something that may be decommissioned a few months after you
> >finish.
> >There won't be *BSD support for a lot of things in OpenJDK6 as it
> >stands,
> >so it'll need backporting from 7.  That may have been feasible a few
> >years
> >ago, but today there doesn't seem much point.
> 
> OpenJDK6/7 are both in the FreeBSD tree. :) Getting this working on
> 6,
> should at least give me the insight to get it working on 7. And thank
> you
> for the head's up.
> >
> >
> Thanks!
> -jgh
> 
> --
> Jason Helfman         | FreeBSD Committer
> jgh at FreeBSD.org       | http://people.freebsd.org/~jgh
> 

-- 
Andrew :)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: 248BDC07 (https://keys.indymedia.org/)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F  8F91 3B96 A578 248B DC07