public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: JacobK622 <JacobK622@protonmail.com>
To: gcc-help Mailing List <gcc-help@gcc.gnu.org>
Subject: Re: I'm really confuesd and frustrated Please Help
Date: Sun, 28 Jun 2020 19:43:38 +0000	[thread overview]
Message-ID: <5mi16ToOmKbHHzMvKTD0udFdwCmoYjPuXctzSH_UmozoE7f8alBqX_Tkj8kN5ucN5lWr_1XWVRaaO4wPxIP6-AynE1BBZWnjqPfsXESzbwc=@protonmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4187 bytes --]

I realize that I did not give much context as to what the original question was so i've included a copy of it at the bottom of this Email. (please read it before continuing)

As far as what ___________________________ said:

"
"If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. " I'll bet you'll find that the public header files for glibc meet the above description, i.e. nothing you use from them is a macro or inline function longer than 10 lines. That means you're safe to ship commercial code that links to glibc in the normal way, and you won't have to release your source code.
"

What I hoped to accomplish with my first email was to avoid having to go through each file in the standard c library and standard c++ library and determine what license each was under.  If I'm reading __________________'s suggestion correctly, I would actually end up doing more work rather than less, because I'd have to count lines of code of each function/method in each file.

As suggested by several people who responded to my email, I'll post this question at libc-help@sourceware.org (which is my understanding of what the correct libc help email is), since it seems like a better place to have this conversation. 

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.

------Original Email Begin------
To gcc-help@gcc.gnu.org

     Firstly I'd like to preface this by saying a few things:

    1. I don't always know what is or isn't socially appropriate to say/ask/do, so please don't get mad at me if I say/ask/do something inappropriate just let me know and I'll try to do better

    2. Sometimes I word things oddly so if a phrase sounds weird or doesn't make sense please let me know and I'll try to explain

    3. I want to make it VERY clear that the above statement should in no way be misinterpreted to say that 'I think you're dumb' because I don't.)
   
    4. I'm not sure this is the correct email to send this to if it isn't:
        a. I'm sorry
        b. Would you please give me the correct email address? Thanks
   
    5. I've been trying to find a solution to this for well over a month now and I'm getting a bit frustrated.
Anyway...

Right now, I have the standard C library and the standard C++ library as installed by gcc and g++, but it appears that I have multiple copies right now on my computer. ( I'm not sure if I have multiple copies, or if just looks that way because it's spread across the computer, or if it's something different.) (I think gcc did this automatically or it could be relatitd to the fact i have both gcc, g++, and mingw installed) This makes it very difficult to know what files are under what licenses, and what files are being included, because I have multiple copies of the same file under different directories. For instance, stdio.h. How do I download the standard C library and the standard C++ library as a separate download so I can put it in a single folder so that it's in one place? I need to keep track of what files I have under what license, and I can be sure that the license is compatible with the license I'd like to distribute my code under.

     I know how to make it ignore the standard search paths and redirect it to a new or add a new search path, I just need to know where I can get a copy of the standard C library and the standard C++ library (gnu gpl with runtime exception or a different non-copyleft license (MIT, BSD(0, 2, or 3 clause), etc)) so i can put them in a single folder.

I have the same questions as applicable to Mingw.

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.
------Original Email End------

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 477 bytes --]

             reply	other threads:[~2020-06-28 19:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-28 19:43 JacobK622 [this message]
2020-06-28 19:53 ` JacobK622
2020-06-28 20:09   ` Paul Smith
2020-06-28 21:30     ` Dan Kegel
  -- strict thread matches above, loose matches on Subject: below --
2020-07-09  3:20 JacobK622
2020-07-09  4:37 ` Dan Kegel
2020-07-08  1:45 JacobK622
2020-07-08  2:01 ` Dan Kegel
2020-07-08  7:12 ` Jonathan Wakely
2020-07-08 19:15   ` Thomas Dineen
2020-07-08 14:49 ` Ian Lance Taylor
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='5mi16ToOmKbHHzMvKTD0udFdwCmoYjPuXctzSH_UmozoE7f8alBqX_Tkj8kN5ucN5lWr_1XWVRaaO4wPxIP6-AynE1BBZWnjqPfsXESzbwc=@protonmail.com' \
    --to=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).