Date: Sat, 17 Mar 2007 18:07:41 -0400
From: Kris Kennaway <kris@obsecurity.org>
To: Garrett Cooper <youshi10@u.washington.edu>
Cc: freebsd-ports@freebsd.org
Subject: Re: Pushing for default jdk / jre to become java/diablo-j{dk,re}
Message-ID: <20070317220741.GA65654@xor.obsecurity.org>
In-Reply-To: <45FC5C00.7070909@u.washington.edu>
References: <45FC4E85.7040005@u.washington.edu> <20070317210507.GA64762@xor.obsecurity.org> <45FC5A27.3050705@u.washington.edu> <45FC5C00.7070909@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 17, 2007 at 02:22:08PM -0700, Garrett Cooper wrote: > Garrett Cooper wrote: > >Kris Kennaway wrote: > >>On Sat, Mar 17, 2007 at 01:24:37PM -0700, Garrett Cooper wrote: > >>>Hello all, > >>> I was just wondering if there was any way where we -- as a group > >>>-- could push to make the default jdk / jre the diablo packaged > >>>versions because frankly I don't want a system to assume that I want > >>>to compile the 1.5 jdk / jre from scratch by first installing the > >>>linux v1.4.2 of the jdk, and having to go through the long and > >>>arduous process of compiling java, for little or no benefit (the only > >>>benefit would be for different architectures that aren't available in > >>>diablo-jdk/-jre, like sparc, powerpc). In that case one would be > >>>required to do the above process. > >>> > >>> It would be nice to add this in though so someone doesn't > >>> accidentally take all that time and disk space compiling all for > >>>naught. > >> > >>Isn't it already the default (except on current where it does not > >>run)? > >> > >>Kris > > > >Oh, duh.. forgot that it doesn't work on -CURRENT. I need to remove Java > >support from OOo then ><.. > > > >Thanks Kris, > >-Garrett > > Gary, > See Kris's previous statement. I miscalculated that I was running > -CURRENT on my devel box and diablo-caffe hasn't been ported to > 7-CURRENT yet. > > All, > Is there some set of steps that are required for building > diablo-caffe? I wouldn't mind releasing some -CURRENT binaries if I could.. The issue is that in 7.0 not all libraries have been bumped yet, even though some of them are incompatible with their 6.x versions (e.g. libthr/libpthread). So 6.x binaries that use those libraries cannot run on 7.0. I raised this issue again the other day and it's been investigated to try and work out what the road blocks are, if any. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070317220741.GA65654>