[klee-dev] The license of runtime/klee-libc

[Daniel Dunbar]

Hi Jonathan,

Where did you derive the author information from?

If you can verify that the implementations we have are from a particular
source then we should probably import their license. If we can't verify the
right source license, then my recommendation would be to try and find BSD
licensed ones we could import (and include license, if need be).

 - Daniel


On Tue, Jun 25, 2013 at 7:01 AM, Jonathan Neuschäfer
<j.neuschaefer at gmx.net>wrote:

> Hello,
>
> the top-level LICENSE.TXT file states:
>
>   The klee software contains code written by third parties.  Such software
> will
>   have its own individual LICENSE.TXT file in the directory in which it
> appears.
>   This file will describe the copyrights, license, and restrictions which
> apply
>   to that code.
>
>   The disclaimer of warranty in the University of Illinois Open Source
> License
>   applies to all code in the klee Distribution, and nothing in any of the
> other
>   licenses gives permission to use the names of the klee Team or Stanford
>   University to endorse or promote products derived from this Software.
>
>   The following pieces of software have additional or alternate copyrights,
>   licenses, and/or restrictions:
>
>   Program             Directory
>   -------             ---------
>   klee-libc           runtime/klee-libc
>
> Yet, runtime/klee-libc doesn't contain a LICENSE.TXT file.
>
> The following files in this directory don't have the standard KLEE
> license comment:
>
>   FILE          COMPLEXITY      AUTHOR
>   atoi.c:       trivial         Berkeley
>   memchr.c:     trivial         Chris Torek / Berkeley
>   memcmp.c:     trivial         Chris Torek / Berkeley
>   stpcpy.c:     trivial         David E. O'Brien / Berkeley
>   strcat.c:     trivial         Berkeley
>   strncmp.c:    trivial         Berkeley
>   strncpy.c:    trivial         Chris Torek / Berkeley
>   strtol.c:     non-trivial     Berkeley
>   strtoul.c:    non-trivial     Berkeley
>
> I propose:
>  - either adding a LICENSE.TXT file to runtime/klee-libc,
>  - or replacing the above files with files that may carry the KLEE
>    license comment.
>
> Please let me know what you think.
>
>
> Thanks,
>  Joanthan Neuschäefer
>
> _______________________________________________
> klee-dev mailing list
> klee-dev at imperial.ac.uk
> https://mailman.ic.ac.uk/mailman/listinfo/klee-dev
>
-------------- next part --------------
HTML attachment scrubbed and removed