Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 5 Feb 2016 09:02:03 +0100
From:      Magnus Ihse Bursie <magnus.ihse.bursie@oracle.com>
To:        Greg Lewis <glewis@eyesbeyond.com>, Brian Gardner <openjdk@getsnappy.com>
Cc:        java@freebsd.org
Subject:   Re: Helping out with JDK 9 on BSD
Message-ID:  <56B456FB.4040707@oracle.com>
In-Reply-To: <20160203034053.GA36170@misty.eyesbeyond.com>
References:  <56ADE7D4.8020107@oracle.com> <56ADE943.6020103@oracle.com> <8B9ACABA-F9B2-4288-9DB5-CA843DE48C34@getsnappy.com> <20160203034053.GA36170@misty.eyesbeyond.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-02-03 04:40, Greg Lewis wrote:
> On Sun, Jan 31, 2016 at 06:57:26AM -0800, Brian Gardner wrote:
>> I???m interested in helping.  I ported openjdk6 to freebsd and also helped out with openjdk8.
>>
>> Brian Gardner
> I'd love to see as much of these changes get into the jdk9 mainline.  My time
> is really limited for the next couple of weeks though.  If it would help you
> or Magnus to use the bsd-port repo to stage changes then that would be
> great too.  Let me do a merge to make sure it is up to date with mainline.
> Notionally we'd have to do a vote to get you both access I think?  But I
> can shepherd changes in if that will help with sharing them.
To make Brian and me committers on the bsd-port project will require a 
community vote with a 2 weeks voting time, yes. Unless Brian already is 
an OpenJDK Author (that is, has an OpenJDK account), getting the account 
created after the vote, has in the past been a long wait for the OpenJDK 
ops to do their thing as well. :(

So the quickest and easiest way, at least if we're just talking a few 
number of patches, is that you shepherd them in.

>
> FWIW, in terms of taking responsibility, I've been regularly updating the
> repos for jdk8 and jdk7 for a couple of years.  I'm happy to keep jdk9
> building if that is what is being looked for there and also port more of
> the BSD changes for jdk8 as appropriate.

I think "regularly building" is kind of the basic they're looking for 
here, and maybe such a promise is good enough to get my build changes 
into the mainline.

Apparently the FreeBSD foundation has a license to use the official TCK 
test suite. Getting a port to completely pass the TCK is likely to be 
quite some work, but if it does it can be integrated as a core supported 
platform in the JDK9 mainline (and then, automatically, in future 
versions of the JDK). Maybe it's not even a requirement to pass the full 
TCK for a community effort. Perhaps it's fine to just run the TCK 
sort-of regularly and tracking the results so that the number of 
failures does not drastically increase, and having some kind of long 
term goal/vision of having zero TCK failures. But I'm not sure about 
these things. We should probably involve Dalibor Topic in that discussion.

/Magnus

>
> - Greg
>
>>> On Jan 31, 2016, at 3:00 AM, Magnus Ihse Bursie <magnus.ihse.bursie@oracle.com> wrote:
>>>
>>> On 2016-01-31 11:54, Magnus Ihse Bursie wrote:
>>>> Hi,
>>>>
>>>> [TL;DR: I'm offering patches to compile JDK 9 on FreeBSD, but it's not clear where to put them, or how.]
>>>>
>>>> I'm working at Oracle on the OpenJDK build team and is responsible for large parts of the build system of OpenJDK. Lately, I've been playing around with FreeBSD (and other BSDs) in my free time, and I've written a patch that will add build system support for FreeBSD, OpenBSD and NetBSD in JDK 9 (tracked in https://bugs.openjdk.java.net/browse/JDK-8147795).
>>>>
>>>> I started writing this when I realized that the jdk9 branch in the OpenJDK bsd-port repository did not contain any BSD-specific changes at all, and the old JDK 8 changes will not readily be portable, due to major changes in the build system between JDK 8 and JDK 9.
>>>>
>>>> I thought it would be a no-brainer to integrate these changes into the JDK 9 mainline, so they would be in place for whenever you guys would start to attack porting the code base. However, some of my collegues thought otherwise. The end result, I think, is that they wanted to see someone (not necessarily a company, the FreeBSD organisation for instance seemed to be okay), to step forward and say "we take responsibility for the BSD port", and give some kind of commitment to actually use these build changes in producing a viable port. You can read the mail conversation here: http://mail.openjdk.java.net/pipermail/build-dev/2016-January/016421.html
>>> I forgot to add that I'm willing to help with build issues for the BSD port, as far as my (like everybode else's) limited free time allows me. Unfortunately, I'm still a noob at BSD internals and can't really help with much apart from that.
>>>
>>> /Magnus
>>>
>>>
>>>> An alternative to pushing this code into the JDK 9 mainline is of course to push it to the bsd-port/jdk9 repo (given that the owners of that repo approves), but that seems like a less favourable solution. Having the code in the mainline does not mean that it gets tested automatically, but it means that it will be part of e.g. refactoring, that would otherwise break a downstream patchset.
>>>>
>>>> I cc:ed this conversation to the bsd-port-dev@openjdk.java.net mailing list, but never got any kind of official response there. Since this list seems more active, I'm trying here instead. :)
>>>>
>>>> So, I'm offering two patches here, one that applies to the build system, is nice and clean, and possible to integrate into JDK 9 mainline, if my collegues are convinced that someone is backing up the BSD port. And there's a second patch, which fixes broken C/C++/Java code and results in a product that can at least run "javac HelloWorld", but this is not yet clean enough for integration anywere, at least not the JDK 9 mainline. (I don't know enough of the BSD internals to fix all problems, so there's some "#if 0" code here and there.)
>>>>
>>>> /Magnus
>>>>
>>>> _______________________________________________
>>>> freebsd-java@freebsd.org mailing list
>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-java
>>>> To unsubscribe, send any mail to "freebsd-java-unsubscribe@freebsd.org"
>>> _______________________________________________
>>> freebsd-java@freebsd.org <mailto:freebsd-java@freebsd.org> mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-java <https://lists.freebsd.org/mailman/listinfo/freebsd-java>;
>>> To unsubscribe, send any mail to "freebsd-java-unsubscribe@freebsd.org <mailto:freebsd-java-unsubscribe@freebsd.org>"
>> _______________________________________________
>> freebsd-java@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-java
>> To unsubscribe, send any mail to "freebsd-java-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56B456FB.4040707>