public inbox for
 help / color / mirror / Atom feed
From: Brian Inglis <>
Cc: "An, Douwa" <>, "" <>
Subject: Re: newlib license question
Date: Tue, 4 Jul 2023 10:01:50 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2023-07-03 21:30, An, Douwa wrote:
> I am struggling with the newlib license since i saw GPL license in git repo.
> It declares that newlib subdirectory is non-GPL related, however, there are GPL code in newlib root directory,&nbsp;
> 1) can we confirm that newlib subdirectory is not infected?&nbsp; which gnu official statement can certify it?&nbsp;
> 2) if I only build baremetal metal newlib, is GPL code used? Can i say newlib I build is non GPL related?


It appears according to licence docs, that Cygwin and Linux targets have LGPL 
components, fr30 target has GPL components, and standards texinfo docs have GFDL 

The rest of newlib should be covered by BSD compatible licences allowing 
commercial use, including files from a number of commercial corps; also newlib 
is contributed to, supported and used by a number of commercial corps, including 
ARM, HP, IBM, Intel, and RedHat, plus many other embedded and RT corps, as part 
of corps commercial products, which may include proprietary modifications or 
components not allowed by copyleft licenses.


Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

  reply	other threads:[~2023-07-04 16:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04  3:30 An, Douwa
2023-07-04 16:01 ` Brian Inglis [this message]
2023-07-04 17:15   ` Jeff Johnston
2023-07-05  1:25 An, Douwa

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).