public inbox for
 help / color / mirror / Atom feed
From: Jeff Johnston <>
Cc: "An, Douwa" <>, "" <>
Subject: Re: newlib license question
Date: Tue, 4 Jul 2023 13:15:17 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 2484 bytes --]

IANAL either.

Some further clarification.  See COPYING.NEWLIB and COPYING.LIBGLOSS for
target-specific licensing for
a newlib/libgloss library built from current sources.

The fr30 is no longer GPL and this is stated in COPYING.NEWLIB.  The linux
target is no longer in the newlib sources and as Brian noted, was LGPL.

For libgloss, the sparc-*leon*, crx-*, cr16-* targets have a GPL with
exception license.  The exception states
that code linked with the libraries built from said sources have no
restrictions.  See the rest of the license
for full explanation of other usages.

The top-level directory files are shared with other gnu projects such as
binutils and gcc.  Configuration and build files
used from there do not affect the licensing of the newlib/libgloss
libraries that are built.

-- Jeff J.

On Tue, Jul 4, 2023 at 12:02 PM Brian Inglis <> wrote:

> 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
> components, fr30 target has GPL components, and standards texinfo docs
> have GFDL
> components.
> 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 17:15 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
2023-07-04 17:15   ` Jeff Johnston [this message]
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 \
    --in-reply-to='' \ \ \ \ \

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