5 ms·
GPLv2 incompatibility does seem like a possible issue. Moving to Apache would make it impossible to ever embed LLVM in the Linux kernel, for example. That might
by azakai 11y ago
GPLv2 incompatibility does seem like a possible issue. Moving to Apache would make it impossible to ever embed LLVM in the Linux kernel, for example. That might seem unnecessary now, but perhaps someday there will be a use for a JIT in the kernel, that we can't foresee.
The same problem might exist with other patent clauses, though - is the Go one compatible with GPLv2?
- pyvpx 11y agosee eBPF
- DannyBee 11y ago"Moving to Apache would make it impossible to ever embed LLVM in the Linux kernel, for example" Because the kernel is GPLv2 only, you also can't embed the GCC JIT, as it's GPLv3. So essentially, you are screwed along multiple axes "but perhaps someday there will be a use for a JIT in the kernel, that we can't foresee." Maybe, but you can't solve every use case on one side. (IE it may be that the kernel may have to have some licensing movement as well)
- azakai 11y agoYes, multiple axes, but this would be a regression for LLVM. In any case, there are other compilers which would remain license compatible with the GPL2, so should the kernel ever need one it could still have one, I guess it just wouldn't be LLVM or GCC.