Re: About adding the new kernel

[Jeff Johnston <jjohnstn at redhat dot com>]

On 16/02/10 05:39 AM, Qiang Wang wrote:
> 2010/2/13 Jeff Johnston<jjohnstn@redhat.com>:
> > On 12/02/10 02:44 AM, Qiang Wang wrote:
> > > hello,Mr. Jeff Johnston
> > >     I use newlib for about 5years, and it is a very good library.
> > >     I just want to confirm if the newlib can add the new GPL RTOS
> > > support which is well used in China and use the customized newlib
> > > libraries.
> > >
> > >    Thank you very much.
> > >
> > > best regards
> > > Wang Qiang
> >
> > Assuming you are talking about an RTOS that is GPL-licensed as opposed to an
> > RTOS named GPL, newlib does not accept GPL-licensed code.  The LGPL license
> > is ok as long as the code is separated from the shared newlib code (i.e. is
> > in its own directory or directories and is only built under specific
> > configurations).  For example, some x86-linux code is under the LGPL
> > license.  This code is in the libc/sys/linux directory and is not built
> > unless one specifies, for example, i686-pc-linux-gnu as the configuration
> > target.
>
> Yes, I mean the RTOS is under GPL-license.The name is
> QingYangOS(www.qingyangos.org) which is used in China and Japan.
> So,  I should release LGPL license codes to newlib.

Actually, BSD-style or less restrictive licenses are recommended as 
often we are talking about a static library (i.e. the code gets linked 
statically with the application).  LGPL is fine for dynamic library 
usage such as is in the case of newlib built for x86-Linux (it uses 
libtool to create a .so library).

Note that you cannot change the existing license of code unless you are 
the writer of the code and you haven't given the rights away to another 
(e.g. your employer).  If you wrote the code, but your employer owns the 
rights, then you must acquire their permission to do so.  If you did not 
write the code, then you will have to contact the owners to get their 
permission to re-license.

> > An RTOS can use newlib and license itself however it wants.  For example,
> > the RTEMS RTOS uses newlib.  RTEMS only adds a little code to newlib with
> > the code checked in adhering to newlib licensing.
>
> I need release some codes to support the kernel, too.
> The code will be with newlib licensing.

Ok.  If you copy code, remember that the license is inherited even if 
you perform modifications.  If you write the code from scratch, you can 
license however you want.  As mentioned, BSD-style is preferred unless 
you are creating a dynamic library version of newlib using libtool.

> > I hope that answers your question.
>
> Thanks for your kindly help.
>
> > Regards,
> >
> > -- Jeff J.
>
>
> Best Regards
> Wang Qiang