Date: Tue, 11 Sep 2012 19:02:58 +0200 From: David Naylor <naylor.b.david@gmail.com> To: toolchain@freebsd.org Subject: Re: Clang as default compiler November 4th Message-ID: <201209111903.01516.naylor.b.david@gmail.com> In-Reply-To: <20120910211207.GC64920@lor.one-eyed-alien.net> References: <20120910211207.GC64920@lor.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart5687862.aMefJreAG0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Monday, 10 September 2012 23:12:07 Brooks Davis wrote: > [Please confine your replies to toolchain@freebsd.org to keep the thread > on the most relevant list.] >=20 > What can you do to help? >=20 > * Switch (some of) your systems. Early adoption can help us find bugs. >=20 > * Fix ports to build with clang. If you don't have a clang system, you > can use the CLANG/amd64 or CLANG/i386 build environments on > redports.org. Hi I know of two ports (wine and libreoffice) that did not work for a clang bu= ilt=20 world (something in libc broke), thus even if those ports were built with g= cc=20 they would fail to run. =20 Has this been fixed, is known to be a problem, or is currently unknown? If= =20 the latter I would gladly check, in the case of wine... =20 Regards --nextPart5687862.aMefJreAG0 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEABECAAYFAlBPbsUACgkQUaaFgP9pFrLjjgCfarJhOlAIUmMGSaqOKV4dqmCZ EWkAn3ZwxZzuzZqpcO9usRogwaARJSbd =03Fv -----END PGP SIGNATURE----- --nextPart5687862.aMefJreAG0--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201209111903.01516.naylor.b.david>