Date: Fri, 11 Jun 2010 13:38:38 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Ed Schouten <ed@80386.nl> Cc: andreast-list@fgznet.ch, "M. Warner Losh" <imp@bsdimp.com>, freebsd-current@freebsd.org Subject: Re: How to disable CLANG & co build in buildworld? Message-ID: <4C129ECE.8040709@FreeBSD.org> In-Reply-To: <20100611203544.GA1797@hoeg.nl> References: <4C128548.8090505@fgznet.ch> <20100611185237.GL56080@hoeg.nl> <20100611.132052.271446115462387749.imp@bsdimp.com> <20100611203544.GA1797@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/11/10 13:35, Ed Schouten wrote: > * M. Warner Losh<imp@bsdimp.com> wrote: >> Except that clang isn't quite disabled when cross-building, due to the >> issue I pointed out when the commit went in wrt bsd.own.mk. >> MACHINE_ARCH is still amd64 until we start to build the sparc64 >> binaries, so anything in the bootstrapping part of the build will not >> be disabled. that's one of many reasons disabling things in >> bsd.own.mk based on architecture is going to fail. > > Exactly. I already mentioned this problem on arch@ back in May. That's > why a small portion of LLVM, namely tblgen, is always built. Even though > this will slightly increase the build time, it shouldn't be excessive. > If someone knows of a nice way to fix this, I am more than willing to > get it fixed. What is "this" that needs to be fixed? Or, asked another way, why are we not optimizing for the common case (building world on the machine that it will be run on)? Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C129ECE.8040709>