Date: Wed, 05 Apr 2017 11:42:16 -0700 From: "Chris H" <bsd-lists@bsdforge.com> To: "FreeBSD CURRENT" <freebsd-current@freebsd.org> Subject: how to mark llvm* forbidden? Message-ID: <67e1da1eb0ff0550aab07f56d1f022ab@ultimatedns.net>
next in thread | raw e-mail | index | archive | help
OK I'm chasing -CURRENT, and I performed an initial install, followed by a new world/kernel && ports about a mos ago. Last Friday, I svn upped the system (src && ports), rebuilt/installed world/kernel. I just began rebuilding the ports, only to find that when finished, I will likely end up with every version of llvm && clang from version 3 to the now current 4. My build session is currently tying nearly every core on the CPU with llvm builds. Given that llvm4 comes in base. Is there *any* reason I can not insist that the ports I upgrade, or build, just use the version(s) of clang/llvm in base? If so. How do I inform the ports that they may *only* use the version(s) in base? Thank you for all your time, and consideration. --Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?67e1da1eb0ff0550aab07f56d1f022ab>