From: Eli Zaretskii <eliz@gnu.org>
To: palves@redhat.com
Cc: simon.marchi@ericsson.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/1] Build GDB as a C++ program by default
Date: Tue, 19 Apr 2016 16:31:00 -0000 [thread overview]
Message-ID: <83zisp7fbl.fsf@gnu.org> (raw)
In-Reply-To: <834max8u8z.fsf@gnu.org> (message from Eli Zaretskii on Tue, 19 Apr 2016 18:59:24 +0300)
> Date: Tue, 19 Apr 2016 18:59:24 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> CC: simon.marchi@ericsson.com, gdb-patches@sourceware.org
>
> > I don't see how linking statically removes the requirement to
> > provide access to sources.
>
> It does, because there's a special clause for that in the L?GPL, whch
> only holds for static linking.
Or maybe I'm wrong and this clause is in the libgcc license, I no
longer remember. But the exemption does exist, and it does cover only
static linking.
next prev parent reply other threads:[~2016-04-19 16:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 17:27 Pedro Alves
2016-04-18 17:27 ` [PATCH 1/1] " Pedro Alves
2016-04-19 7:34 ` Yao Qi
2016-04-19 13:34 ` [PATCH 0/1] " Simon Marchi
2016-04-19 14:18 ` Pedro Alves
2016-04-19 14:48 ` Eli Zaretskii
2016-04-19 15:03 ` Pedro Alves
2016-04-19 15:23 ` Eli Zaretskii
2016-04-19 15:40 ` Pedro Alves
2016-04-19 15:59 ` Eli Zaretskii
2016-04-19 16:20 ` Pedro Alves
2016-04-19 16:31 ` Eli Zaretskii [this message]
2016-04-19 15:41 ` Simon Marchi
2016-04-19 16:32 ` Eli Zaretskii
[not found] ` <AC542571535E904D8E8ADAE745D60B19445B1C11@IRSMSX104.ger.corp.intel.com>
[not found] ` <5716425B.3050707@intel.com>
[not found] ` <57164325.8020408@redhat.com>
2016-04-19 15:20 ` Walfred Tedeschi
2016-04-20 19:56 ` Pedro Alves
2016-04-20 22:16 ` Pedro Alves
2016-04-21 15:18 ` John Baldwin
2016-04-21 16:41 ` Pedro Alves
2016-04-19 15:47 ` Simon Marchi
2016-04-19 15:50 ` Pedro Alves
2016-04-20 22:27 ` Pedro Alves
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=83zisp7fbl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.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