Hacker News new | ask | show | jobs
by silverpikezero 3705 days ago
I don't know why you are getting downvoted. Clause #2 would require the inclusion of the BSD license with any release of compiled code. This is a very serious issue with the library. Any additional licensing terms which must be propagated to the compiled software is bad juju.
1 comments

What are you talking about? Every open source license I can think of requires you to distribute the license with your binary: GPL, LGPL, BSD, MIT, Apache, etc.
The vast majority of compiler runtime libraries have explicit exceptions to licenses to avoid this, to avoid creating copyright infringers out of everyone.
So? You just don't use Cilk if you don't want to include the license, just like a normal library. It is a language extension, not something that magically infects your regular C or Fortran code...
Is this true for MIT? BSD, for example, explicitly mentions binary distribution but MIT does not.
The MIT license says "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software." I would think that a binary distribution would count as a "copy or substantial portion of the Software", but I'm not a lawyer.

Full text:

Copyright (c) <year> <copyright holders>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.