Date: Wed, 11 Sep 2019 16:34:11 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 240507] WITHOUT_CLANG=yes WITH_CLANG_BOOTSTRAP=yes does not work Message-ID: <bug-240507-29464-d6fCmmJtO7@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-240507-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-240507-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240507 --- Comment #3 from Kyle Evans <kevans@freebsd.org> --- (In reply to Dimitry Andric from comment #2) > The problem with that is that a lot of unused targets will be built, whic= h is why the MK_LLVM_TARGET_ knobs were created in the first place. Ideall= y, only the minimum set of targets is built. Right... so this all feels like a good opportunity for foot shooting. =3D\ = It'd be nice if we had some way of listing the targets that `cc` supports, so we= can decide if we need to bootstrap a cross-compiler that works for what we're trying to build and we can at least force *that* option on for the bootstrap compiler. The last time I checked, one could turn off all of the LLVM_TARGET_* knobs except, say, LLVM_TARGET_X86. They install a machine that way, and the mach= ine has all of the knobs except LLVM_TARGET_X86 turned off just like the builde= r. A cross-build of aarch64 would then just error out with 'target triple unknow= n' or something to this effect, rather than being able to detect- "oh yes, the host isn't functional for this." --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-240507-29464-d6fCmmJtO7>