Date: Sat, 27 Mar 1999 20:02:38 -0800 (PST) From: Mark Diekhans <markd@Grizzly.COM> To: alk@pobox.com Cc: freebsd-java@FreeBSD.ORG Subject: Re: A BSD-licensed JIT (was Re: Development Projects) Message-ID: <199903280402.UAA03993@osprey.grizzly.com> In-Reply-To: <14077.41181.542222.948279@avalon.east> (message from Anthony Kimball on Sat, 27 Mar 1999 21:30:25 -0600 (CST)) References: <Pine.OSF.4.02.9903271116530.22203-100000@fly.HiWAAY.net> <199903271801.KAA10685@osprey.grizzly.com> <14077.41181.542222.948279@avalon.east>
next in thread | previous in thread | raw e-mail | index | archive | help
>Quoth Mark Diekhans on Sat, 27 March: >: Given that FreeBSD is fairly dependent on GPL-ed code anyway (e.g. gcc) and >: the way a JIT is licensed has no impact (that I can see) on its use, it >: doesn't seem near as important as just having a really solid java environment. > >Open question: Can you distribute a JDK binary (whether new "Sun >Community Source License" a la 1.2 or old 1.1.7-style) with a JIT >which is GPL? JITs for the Sun JDK are dynamically loaded shared libraries, so they can be distrbuted independently. LGPL is probably no issue; as far as I can tell, the GPL makes little sense in a world that decomposes into something more complex than staticly linked programs. >My take: No. You absolutely cannot. You are clearly violating the >GPL if you will not provide source, and the Sun license prevents >you from providing source. > >I don't think LGPL will allow it either. > >The closest you can come is to provide instructions to the consumer >for integrating the GPL JIT into a binary JDK. > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-java" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903280402.UAA03993>