NetBSD Problem Report #46340

From  Mon Apr 16 21:08:57 2012
Return-Path: <>
Received: from ( [])
	by (Postfix) with ESMTP id 3BC4563B915
	for <>; Mon, 16 Apr 2012 21:08:57 +0000 (UTC)
Message-Id: <>
Date: Mon, 16 Apr 2012 21:08:56 +0000 (UTC)
Subject: lang/openjdk7: DragonFlyBSD port
X-Send-Pr-Version: www-1.0

>Number:         46340
>Category:       pkg
>Synopsis:       lang/openjdk7: DragonFlyBSD port
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    marino
>State:          closed
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 16 21:10:00 +0000 2012
>Closed-Date:    Tue May 15 05:41:07 +0000 2012
>Last-Modified:  Tue May 15 05:41:07 +0000 2012
>Originator:     Chris Turner
>Release:        n/a
n/a (dragonfly) or:

DragonFly 3.1-DEVELOPMENT DragonFly v3.1.0.312.g538810-DEVELOPMENT #26: Thu Mar 15 22:01:06 GMT 2012  i386

and also x86_64, v2.11 and 3.0

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:

With my initial i386 version under

The subtrees also contain the openjdk bootstrap tarballs as provided for
in the 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.





From: "OBATA Akio" <>
Subject: Re: pkg/46340: lang/openjdk7: DragonFlyBSD port
Date: Wed, 25 Apr 2012 18:20:12 +0900

 IMO, bootstrap binaries must be created by authorized person (pkgsrc or DragonFly developer),
 and put on pkgsrc's MASTER_SITE_LOCAL, or DragonFry's master site (
 That's all.

 I don't know which is preferred approach for DraognFly folks.

 OBATA Akio /

From: Chris Turner <>
Subject: Re: pkg/46340: lang/openjdk7: DragonFlyBSD port
Date: Thu, 10 May 2012 13:32:08 -0500

 Hello -

 Do not know how I missed this update about the bootstrap -

 I will discuss the options with the DragonFly people
 and see what is preferable as it sounds like either
 option is suitable for pkgsrc.


Responsible-Changed-From-To: pkg-manager->marino
Responsible-Changed-When: Sat, 12 May 2012 12:02:13 +0000
We are testing an updated version of this submission which is advertised to work on both supported DragonFly platforms.  Once confirmed, DragonFly support of openjdk7 will be committed.

State-Changed-From-To: open->closed
State-Changed-When: Tue, 15 May 2012 05:41:07 +0000
DragonFly support committed, Chris Turner was involved was the final changeset.


NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD:,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.