This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: CodeSourcery's licensing of newlib files
- From: Joel Sherrill <joel dot sherrill at oarcorp dot com>
- To: Gregory Fong <gregory dot 0xf0 at gmail dot com>, freddie_chopin <freddie_chopin at op dot pl>
- Cc: "newlib at sourceware dot org" <newlib at sourceware dot org>
- Date: Wed, 23 Oct 2013 15:13:11 -0500
- Subject: Re: CodeSourcery's licensing of newlib files
- Authentication-results: sourceware.org; auth=none
- References: <52002514-06af832aa02dd5da957c6e7accaca7d4 at pmq1v dot m5r2 dot onet> <CADtm3G7S6Pjch8BQ+P8THt+8kfFX30xeswR6NT2CjifegVWwqg at mail dot gmail dot com>
On 10/23/2013 3:09 PM, Gregory Fong wrote:
> On Wed, Oct 23, 2013 at 6:03 AM, freddie_chopin <freddie_chopin@op.pl> wrote:
>> Hello!
>>
>> Currently I have an opportunity to work with CodeSourcery's ARM toolchains in the "full" (paid) version. The thing that caught my eye is the strange license of the header files, that are - of course - newlib files...
>>
>>
>> stdint.h
>> ---
>>
>> /* This file is part of the CodeSourcery C Library (CSLIBC).
>>
>> Copyright (c) 2009 CodeSourcery, Inc.
>>
>> THIS FILE CONTAINS PROPRIETARY, CONFIDENTIAL, AND TRADE SECRET
>> INFORMATION OF CODESOURCERY AND/OR ITS LICENSORS.
>> [snip]
>>
>> and so on... Can they attach sth like that to newlib's files?
>
> Yes, that's permitted under the BSD license.
>
Not all code in newlib is BSD licensed but the others likely allow it
also.
Permitted doesn't make it cool or nice.
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985