Date: Tue, 5 Mar 2019 13:51:59 -0500 From: Robert Huff <roberthuff@rcn.com> To: Charlie Li <ml+freebsd@vishwin.info> Cc: Robert Huff <roberthuff@rcn.com>, Jan Beich <jbeich@FreeBSD.org>, freebsd-ports@freebsd.org Subject: Re: [HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT Message-ID: <23678.50511.741276.774471@jerusalem.litteratus.org> In-Reply-To: <40777eb4-532b-35ce-6773-635655a58e0d@vishwin.info> References: <y35u-xm2v-wny@FreeBSD.org> <23677.47024.212159.5967@jerusalem.litteratus.org> <pnr6-chbd-wny@FreeBSD.org> <23677.63535.186279.730742@jerusalem.litteratus.org> <40777eb4-532b-35ce-6773-635655a58e0d@vishwin.info>
next in thread | previous in thread | raw e-mail | index | archive | help
Charlie Li <ml+freebsd@vishwin.info> writes: > The LLVM ports are still needed for those consumers that need their > components, such as llvm-config and the like. Please refer to the aptly > named wiki page again: > https://wiki.freebsd.org/WhyDoIHaveToBuildLLVMWhenIAlreadyHaveClangInstalled This was the thing I thinking about. > Think of it this way: the base system toolchain is *based on* some > released version of LLVM (or GCC) as of a particular revision of > base/. "Based on" means that components that are not critical to > the actual functioning of the toolchain or otherwise useful to > FreeBSD itself are bound to be stripped away when included and > integrated in the base system. That may be the path of wisdom; and I understand keeping things working is a non-trivial job, for which I thank those who do it. Please understand my ... frustration ... in having to deal with the conseqences, particularly with regard to the ongoing drm changes. To return to my original point, this is why I suggested an entry in ports/UPDATING - to let others in my position know of possible impact. Respectfully, Robert Huff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23678.50511.741276.774471>