> On Dec 18, 2014, at 6:34 AM, owner-freebsd-...@freebsd.org wrote: > > > Dimitry Andric writes: > >>> - Could a "MK_CLANG_ALL_TARGETS" or something similar option be >>> added to src.opts.mk to fine tune this process for those of us who >>> don't want to build a cross-compile toolchain every iteration for our >>> target MACHINE/MACHINE_ARCH? >> >> I would be fine with something like this, as long as it is turned off by >> default, or if it is only used for the bootstrap stages. It is actually >> an extremely useful feature of clang that you can target multiple >> architectures with one compiler binary. > > Point of information: this seems useful for developers, and > (almost entirely) useless for everyone else. Are there other > cohorts that want this badly? > If that's correct, and there's a simple switch for > configuration ... why should this default to what's useful for the > (much?) smaller number of people? About what am I ignorant?
Only people working on a single binary of clang to build all architectures are interested, which is a vanishingly small number. There’s little point to build this stuff even for hard-core developers. Warner
signature.asc
Description: Message signed with OpenPGP using GPGMail
