Date: Fri, 29 Aug 2003 14:32:55 -0700 From: "David O'Brien" <obrien@FreeBSD.org> To: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/gnu/usr.bin Makefile src/lib Makefile src/sbin Makefile src/usr.bin Makefile src/usr.sbin Makefile Message-ID: <20030829213255.GB71225@dragon.nuxi.com> In-Reply-To: <20030829200349.GA86217@wombat.localnet> References: <200308291035.h7TAZ1Wm008611@repoman.freebsd.org> <Pine.NEB.3.96L.1030829090446.44583A-100000@fledge.watson.org> <20030829183759.GA68755@dragon.nuxi.com> <20030829121043.K43708@root.org> <20030829194007.GA69823@dragon.nuxi.com> <20030829200349.GA86217@wombat.localnet>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 29, 2003 at 04:03:50PM -0400, Michael Edenfield wrote: > > > > > > NO_TOOLCHAIN skips Compilers and Binutils ... > > I disagree that it should be a single (MINIMAL(sp?)) knob. But that > > there should be more discussion about it. If you have NO_TOOLCHAIN set, > > I can't think of a reason to have /usr/include or /usr/lib/*.a populated; > > for instance. > > If you don't have a compiler or binutils toolchain installed, then make > buildworld isn't going to make it very far in general :) Yes that is obvious. When one sets NO_TOOLCHAIN they are obviously building world on a workstation and doing the 'make installworld' with a destination on the "embedded" machine. If NO_TOOLCHAIN is set, it is OK to assume a [mostly] complete world on the build machine and that it matches the sources being built. NO_TOOLCHAIN however, would keep from installing compiler, /usr/include/*, and /usr/lib/*.a. Also any optimization of 'make buildworld' time should occur knowing that things like lib*.a won't be used or installed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030829213255.GB71225>