Re:Consider LibreSSL as default OpenSSL provider again
by chasil on Thursday November 18, 2021 @03:01PM
(#29269713)
Clang is now used on the x86-64 variant of OpenBSD.
I'm fairly confident that gcc is still available in the ports collection.
On architectures that clang doesn't support, it's (likely) still gcc.
Re:Consider LibreSSL as default OpenSSL provider again
by krylon on Thursday November 18, 2021 @04:58PM
(#29271159)
I know. Last time I checked, gcc still was the default C compiler on architectures clang did not support, but it was a couple years ago, and they discontinued a few architectures since (vax, alpha, probably others?).
Yes, gcc is still available through ports/packages, but the point was if it's okay to distribute GPL code as part of the base system if the base as a whole is BSD/MIT licensed.
Re:Consider LibreSSL as default OpenSSL provider again
by chasil on Friday November 19, 2021 @01:14AM
(#29274361)
Within the BSD realm, the GPL is frowned upon, and there is a current moving away from it.
Re:Consider LibreSSL as default OpenSSL provider again
by anthk on Thursday November 18, 2021 @02:03PM
(#29269127)
OpenBSD discarded base gcc. Now they are pro-ISC everywhere.
They included gcc for convenience in some architectures.
Re:Consider LibreSSL as default OpenSSL provider again
by krylon on Thursday November 18, 2021 @02:52PM
(#29269613)
I know, but they included it for a pretty long time, so I think distributing GPL code as part of a BSD project is kosher, legally speaking. (Same goes for FreeBSD, although they, too, replaced gcc with clang some time ago.)
I'm not taking sides here, the OpenBSD developers have famously stopped supporting hardware when the vendors did not supply documentation under acceptable conditions. They obviously are very serious about the "Open" part.