From: Mark Wielaard <mark@klomp.org>
To: Elena Zannoni <elena.zannoni@oracle.com>
Cc: frysk@sourceware.org
Subject: Re: Disassembly source buffer and libopcodes
Date: Wed, 22 Aug 2007 18:13:00 -0000 [thread overview]
Message-ID: <1187806402.3759.34.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <46CC5DF2.6060909@oracle.com>
Hi Elena,
On Wed, 2007-08-22 at 12:01 -0400, Elena Zannoni wrote:
> Thanks, I see Andrew replied to that thread, so what is the impact on
> frysk?
> Do we switch to GPLv3 or just ignore since we have our copy of
> libopcodes (and keep that at GPLv2?)
Unfortunately neither is an option atm :{
We have one other GPLv2-only dependency elfutils. elfutils does have the
same special exception for linking it with eclipse code into a larger
work as frysk has, but binutils/libopcodes is GPL-only and unfortunately
the EPL isn't GPL compatible (neither with version 2 nor version 3).
So we have to either ditch the EPL eclipse code (so the exception isn't
needed and we can just use pure GPL), ask the Eclipse people to dual
license under the GPL, or find an disassembler that is compatible with
both the GPL and EPL code.
Cheers,
Mark
prev parent reply other threads:[~2007-08-22 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 12:26 Mark Wielaard
2007-08-22 14:27 ` Elena Zannoni
2007-08-22 14:51 ` Mark Wielaard
2007-08-22 16:02 ` Elena Zannoni
2007-08-22 18:13 ` Mark Wielaard [this message]
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=1187806402.3759.34.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=elena.zannoni@oracle.com \
--cc=frysk@sourceware.org \
/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).