From: Dan Kegel <dank@kegel.com>
To: JacobK622 <JacobK622@protonmail.com>
Cc: gcc-help Mailing List <gcc-help@gcc.gnu.org>
Subject: Re: I'm really confuesd and frustrated Please Help
Date: Tue, 7 Jul 2020 19:01:11 -0700 [thread overview]
Message-ID: <CAPF-yOYp9pqsbUNhc5B55dR+4En8qV3xWNAgsS51ZqCyUzsztg@mail.gmail.com> (raw)
In-Reply-To: <TZ4Ge6DPj-PCm1a67vxFck7DIj2adqXZSgjlRgAq4K2xM8gR6bTX0akzctWMFlk3cJkB8SdlQ3oXVCnF7VBGlmY7lzAp0YZrZT0D_esHaNw=@protonmail.com>
If you're using gcc and glibc in any halfway normal manner,
and you want to distribute your binaries to customers, but not release your
source code,
that's ok.
If you're doing anything strange, you might need to double-check.
But in general, glibc is designed to avoid any worries about open source
forcing you to release your source code in the great majority of cases.
- Dan
On Tue, Jul 7, 2020 at 6:46 PM JacobK622 via Gcc-help <gcc-help@gcc.gnu.org>
wrote:
> to: gcc help mailing-list
>
> I'm still a bit concerned about this.
>
> What are my obligations under the licenses? (or should I post that as a
> new question?)
>
> Does anyone else have any thoughts on this?
>
> My email is JacobK622@protonmail.com feel free to email me at any
> time,although I may not respond immediately. (usually within 24hrs.)
>
> From, Jacob K
>
> Sent with ProtonMail Secure Email.
next prev parent reply other threads:[~2020-07-08 2:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 1:45 JacobK622
2020-07-08 2:01 ` Dan Kegel [this message]
2020-07-08 7:12 ` Jonathan Wakely
2020-07-08 19:15 ` Thomas Dineen
2020-07-08 14:49 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2020-07-09 3:20 JacobK622
2020-07-09 4:37 ` Dan Kegel
2020-06-28 19:43 JacobK622
2020-06-28 19:53 ` JacobK622
2020-06-28 20:09 ` Paul Smith
2020-06-28 21:30 ` Dan Kegel
2020-06-27 15:50 JacobK622
2020-06-27 17:45 ` Dan Kegel
2020-06-27 17:52 ` Paul Smith
2020-06-27 18:30 ` Jonathan Wakely
2020-06-11 1:26 JacobK622
2020-06-11 2:03 ` Dan Kegel
2020-06-11 8:39 ` Jonathan Wakely
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=CAPF-yOYp9pqsbUNhc5B55dR+4En8qV3xWNAgsS51ZqCyUzsztg@mail.gmail.com \
--to=dank@kegel.com \
--cc=JacobK622@protonmail.com \
--cc=gcc-help@gcc.gnu.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).