Date: Tue, 12 Feb 2013 18:19:49 -0500 From: Eitan Adler <lists@eitanadler.com> To: Niclas Zeising <zeising+freebsd@daemonic.se> Cc: Ian FREISLICH <ianf@clue.co.za>, Steve Kargl <sgk@troutmask.apl.washington.edu>, freebsd-current@freebsd.org Subject: Re: 7+ days of dogfood Message-ID: <CAF6rxgk0UK4Hvj4hNOrMh1ADemsWwQjtu_tiuz9sUo0st5bbQg@mail.gmail.com> In-Reply-To: <511AC875.1000704@daemonic.se> References: <20130210000723.GA73630@troutmask.apl.washington.edu> <E1U4QTd-0003BM-7s@clue.co.za> <511AC875.1000704@daemonic.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12 February 2013 17:55, Niclas Zeising <zeising+freebsd@daemonic.se> wrote: > On 02/10/13 07:33, Ian FREISLICH wrote: >> 1. WITHOUT_CLANG_IS_CC=yes >> I don't think clang is ready for prime time in FreeBSD, or FreeBSD >> isn't ready to use clang in prime time. I got a new laptop (ASUS >> UX31A) and found that a lot of the ports I needed to install >> didn't compile or core dumped. (Sorry I didn't report these to >> the project). >> This option sorted that problem out. However you will need to >> rebuild everything including world and kernel with gcc before >> you start building ports with gcc or you will still have problems. > > Please please please report ports that fail with clang to ports@ or the > ports maintainer or both. If this is not done, then the problems will > never get fixed (regardless whether it is bad/broken code in the port or > a bug in clang). Actually, please file a PR: don't email people privately. The point remains: If this is not done, then the problems will never get fixed -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgk0UK4Hvj4hNOrMh1ADemsWwQjtu_tiuz9sUo0st5bbQg>