https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63651
--- Comment #9 from howarth at bromo dot med.uc.edu --- (In reply to Eric Gallager from comment #8) > (In reply to howarth from comment #7) > > > > If I remember correctly, the blocks issue is problematic because of the > > blocks runtime's license, so that whole package would have to be reverse > > engineered to be under GPLv3, no? > > I just googled the text of the license for the blocks runtime (i.e. > libclosure), and it looks like it's the MIT license... can't MIT-licensed > packages be used in GPLed projects? After accounting for the ambiguity of > the name, the GNU license list seems to say they're compatible: > > https://www.gnu.org/licenses/license-list.html#X11License > or > https://www.gnu.org/licenses/license-list.html#Expat > > The libclosure license can be found at the top of: > http://opensource.apple.com/source/libclosure/libclosure-65/ > BlockImplementation.txt > or > http://opensource.apple.com/source/libclosure/libclosure-65/BlockSpec.rtf > (if anyone wants to verify) The relevant files are those in compiler-rt/lib/BlocksRuntime. There are only three files and those all have an Apple license... * Copyright 2008-2010 Apple, Inc. 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.
