From: David Anderson <davea42@linuxmail.org>
To: gdb@sourceware.org
Subject: crc32, gpl, debuglink, and interoperability.
Date: Fri, 9 Oct 2020 13:59:17 -0700 [thread overview]
Message-ID: <6eeb0949-c85a-9762-37b0-f08a49b8ba90@linuxmail.org> (raw)
I'm the maintainer of libdwarf and dwarfdump and wish to
interoperate with gdb/debuglink by reading the appropriate
sections and validating the crc32 when appropriate.
The crc32 used in binutils for debuglink is under plain GPLV3.
Linking to sucn a thing (from what I've been able to find and
somewhat-understand) means the GPL applies to the linked work.
That is not appropriate for the libdwarf library.
So how can I get permission to use LGPL v2.1 (which most of
libdwarf is) or LGPL v3? on the relevant crc32 function (in
bfd/opncls.c)? In other words extract the source and apply
an LGPL to the one function calculating the debuglink crc.
At present interoperability with debuglink is impossible in
libdwarf (so impossible in dwarfdump) and I would like to
make it work.
Thanks for any help or information.
David Anderson
--
Of course power tools and alcohol don't mix.
Everyone knows power tools aren't soluble in alcohol.
-- Crazy Nigel
next reply other threads:[~2020-10-09 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 20:59 David Anderson [this message]
2020-10-09 21:36 ` 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=6eeb0949-c85a-9762-37b0-f08a49b8ba90@linuxmail.org \
--to=davea42@linuxmail.org \
--cc=gdb@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).