Date: Sat, 21 Jan 2012 13:33:01 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-questions@freebsd.org Subject: Re: Clang - what is the story? Message-ID: <4F1ABE8D.2090906@infracaninophile.co.uk> In-Reply-To: <4F1AAB66.5070100@herveybayaustralia.com.au> References: <4F1AAB66.5070100@herveybayaustralia.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB93A7172E83B6C8DCDA09437
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 21/01/2012 12:11, Da Rock wrote:
> I've been seeing a lot of hoorays and pats on the back and a general
> feeling satisfaction in being able to use clang to compile FreeBSD and
> ports. The only reason I can see from searching is a need to get away
> from gcc (which is tried and tested since the beginning of time) which
> is now apparently GPLv3.
>=20
> Can someone offer some clarity as to the importance of this? I'm
> guessing the that stepping away from GPL is generally a good thing,
> especially if there is something similar with similar license structure=
> to BSD; I just can't understand the rush of it.
The problem is exactly the GPLv3. The version of gcc in the base system
is gcc-4.2, the last version licensed under the old GPLv2 terms, but now
looking quite elderly and not resulting in the best performance.
> Even under GPL anything built using gcc can be licensed as you like, so=
> I doubt it could be that.
>=20
> I'm not skeptical, just curious- trying to get my head around some of
> the dev side of things :)
Unfortunately, no -- you can't necessarily license anything compiled
with a GPLv3 compiler using whatever license you prefer. For instance,
one problem is that executables will be linked against libraries which
are part of the compiler -- and the viral nature of GPLv3 means that the
resulting programs have in their turn to be licensed under GPLv3.
That's not acceptable for FreeBSD, hence the decision to switch to a BSD
licensed toolchain using clang.
9.0 is really an intermediate step in the changeover -- gcc and clang
are both provided in the base system and its a matter of administrative
choice which one is chosen for compiling the system. One consequence of
the change is that it will become more common to install a recent
version of gcc from ports to facilitate compiling gcc-only software,
with the rest of ports typically compiled with either that ports-gcc or
the base clang. This is fairly new at the moment, and there still needs
to be a deal of debugging effort put into making the ports work well
with compilers other than the base gcc-4.2.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew@infracaninophile.co.uk Kent, CT11 9PW
--------------enigB93A7172E83B6C8DCDA09437
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8avpUACgkQ8Mjk52CukIynVACgiSENDLBRLZSzNQpVFAvM1+jd
oQMAnjhn0wdfr3aNht0tJRriHtyNj/bC
=BJ/k
-----END PGP SIGNATURE-----
--------------enigB93A7172E83B6C8DCDA09437--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F1ABE8D.2090906>