pkg/46340: lang/openjdk7: DragonFlyBSD port

[c.turner%199technologies.com@localhost]

>Number:         46340
>Category:       pkg
>Synopsis:       lang/openjdk7: DragonFlyBSD port
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 16 21:10:00 +0000 2012
>Originator:     Chris Turner
>Release:        n/a
>Organization:
>Environment:
n/a (dragonfly) or:

DragonFly dev01.lan1.tx.199technologies.com 3.1-DEVELOPMENT DragonFly 
v3.1.0.312.g538810-DEVELOPMENT #26: Thu Mar 15 22:01:06 GMT 2012     
root%dev01.lan1.tx.199technologies.com@localhost:/usr/obj/usr/src/sys/GENERIC  
i386

and also x86_64, v2.11 and 3.0
>Description:

Builds of lang/openjdk7 has been broken on DragonFlyBSD intermittently,
and additionally previously only was bootstrapped through on the i386 platform.

After some work ~1/2012, I was able to bootstrap openjdk7 on both i386 and 
x86_64 DragonFlyBSD via the route of kaffe (jdk1.4), wip/jdk15 and wip/jdk16 
(due to lack of redistributable bootstraps this path is needed).

My final pkgsrc subtree (builds on i386 and x86_64 dragonflybsd) is available 
on:

http://leaf.dragonflybsd.org/~cat/df-jdk/pkgsrc-i386-x64/openjdk7/

With my initial i386 version under 

http://leaf.dragonflybsd.org/~cat/df-jdk/pkgsrc-i386/

The subtrees also contain the openjdk bootstrap tarballs as provided for
in the bootstrap.mk logic.

Since some discussion would be needed about how to host / maintain these binary 
bootstraps, and possibly more 'proper' integration might be needed before final 
inclusion, this bug is submitted without a simple 'patch' but instead with the 
web references as outlined above,
so that the bug might become a discussion, leading up to a final solution / 
patch / etc. for inclusion into the tree.

As a side note, I have discussed this with John Marino (pkgsrc comitter for 
dragonfly), and Francois Tigeot who had done the initial work of getting the 
i386 bootstrap up and running previously. They were als able to properly 
reproduce the build in their environment, fwiw.

Similarly, I was able to reproduce the i386 build on NetBSD-5, but
the x86_64 build did not complete on a 6-dev (5.99) x86_64 build approx. 1 
month ago.

Rather than let the build languish, I thought it best to get the 'ball rolling' 
on integrating the Dragonfly work so that it can be maintained 'in-tree' as 
part of regular package maintentance. 

Any feedback / needed integration is welcome to this end.

Thanks







>How-To-Repeat:

>Fix: