This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On 6/28/19 7:57 PM, Mark Geisert wrote: > > Please forgive my ignorance of licensing details... Are we allowed to > copy GNU library source into Cygwin? Cygwin is a different beast (it has GPL code, but still tries to avoid wholesale imports from glibc, preferring to copy from BSD where possible). But you asked a question on the newlib list, and here the answer is a definitive now - newlib cannot include [L]GPL code, so copying from glibc is forbidden. > Or is re-implementation from > documentation the way to go? Correct, unless you can find an existing BSD implementation with appropriate semantics to copy. > In either case, must the glibc file > organization be followed or is platform-specific rejiggering acceptable? The more you copy glibc's layout, the more questionable it is on whether you did inappropriate copying. What matters more is getting something that implements the right semantics. > > I'd like to just add the CPU_SET macros to Cygwin's new sys/cpuset.h and > any needed support code to our sched.cc but am willing to hear other > options. > Thanks, > > ..mark > -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |