News for hackers. Stuff that matters.
Re:The State of Toolchains in OpenBSD by webaholic on Wednesday May 19, 2021 @08:03PM (#27215929)
Why was the compromise made for LLVM 10 with the Apache license and not for GCC with the v3 GPL license?
Re:The State of Toolchains in OpenBSD by wahern on Wednesday May 19, 2021 @08:24PM (#27216032)
No compromise, AFAIU. They felt they had no choice but to upgrade to a more modern compiler, and they preferred clang+APL2 over gcc+GPLv3. Apache 2.0 still violates their licensing policy. Technically, GPLv2 also violated their licensing policy. They historically used GPL'd software like gcc when there were no viable alternatives and doing without wasn't acceptable either.

EDIT: See https://marc.info/?l=openbsd-misc&m=159514079929237&w=2

Re:The State of Toolchains in OpenBSD by mwfunk on Wednesday May 19, 2021 @08:15PM (#27215984)
I would imagine that many or most (or all?) OpenBSD developers consider the Apache license less than ideal but GPLv3 counterproductive or even malicious. Not a tough choice from that perspective. I'm not advocating for or against anything, just stating common reasoning amongst BSD folks.
Re:The State of Toolchains in OpenBSD by protomyth on Wednesday May 19, 2021 @08:10PM (#27215951)
Probably because of the drm code requirements and only having a choice between GPL v3 (gcc) or Apache 2 (llvm).