From: Robert Schuster <thebohemian@gmx.net>
To: Mark Wielaard <mark@klomp.org>
Cc: Sal <svferro@gmail.com>, java@gcc.gnu.org
Subject: Re: GCJ with OpenJDK Java API instead of GNU Classpath
Date: Fri, 08 May 2009 13:47:00 -0000 [thread overview]
Message-ID: <4A043760.4060908@gmx.net> (raw)
In-Reply-To: <1241713710.3769.8.camel@fedora.wildebeest.org>
[-- Attachment #1: Type: text/plain, Size: 433 bytes --]
Hi,
Mark Wielaard schrieb:
> On Wed, 2009-05-06 at 15:41 -0600, Sal wrote:
>> - Are there licensing issues with linking OpenJDK to other code via GCJ?
>
> The only legal issue is that GNU Classpath is GPLv2+ and OpenJDK is
> GPLv2 only, so you loose GPLv3 compatibility.
maybe a project wanting to use OpenJDK under GPLv2+ would create the
incentive for Sun to look into fixing this incompatibility.
Regards
Robert
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2009-05-08 13:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 20:43 Sal
2009-05-07 9:17 ` Andrew Haley
2009-05-07 11:45 ` Bryce McKinlay
2009-05-07 13:25 ` Andrew John Hughes
2009-05-07 13:43 ` Andrew Haley
2009-05-07 13:50 ` Bryce McKinlay
2009-05-07 20:24 ` Sal
2009-05-08 8:04 ` Robert Schuster
2009-05-08 10:08 ` Andrew Haley
2009-05-07 16:28 ` Mark Wielaard
2009-05-08 13:47 ` Robert Schuster [this message]
2009-05-07 14:31 Chris Gray
2009-05-07 15:29 ` Andrew John Hughes
2009-05-07 16:25 ` Mark Wielaard
2009-05-07 16:32 ` Andrew Haley
2009-05-07 17:10 ` Mark Wielaard
2009-05-07 17:20 ` Andrew Haley
2009-05-07 17:24 ` David Boreham
2009-05-07 17:34 ` Andrew Haley
2009-05-07 17:44 ` Mark Wielaard
2009-05-08 0:22 ` Andrew John Hughes
2009-05-08 10:13 ` Andrew Haley
2009-05-08 11:00 ` Mark Wielaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A043760.4060908@gmx.net \
--to=thebohemian@gmx.net \
--cc=java@gcc.gnu.org \
--cc=mark@klomp.org \
--cc=svferro@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).