> On Mon, 25 Sep 2006 11:34:42 -0700, "Kevin Oberman" <oberman@es.net> wrote: > >2. Building a kernel with config is not officially supported. It's at > your risk and may not work in all cases. Build a kernel with: > cd /usr/src > make buildkernelI was not aware that you wern't supposed to use config anymore - and I am not convinced that the suggested alternative is actually a replacement as I thought that buildkernel required you to have built the world first ? Is this no longer true ? If it *is* true thhen what is the alternative to using 'config' which should be used if you are on a system where you do not have the time or the disc space to rebuild the world and simply want to recompile the kernel ? -pete.
On Tue, Sep 26, 2006 at 11:23:49AM +0100, Pete French wrote:> > On Mon, 25 Sep 2006 11:34:42 -0700, "Kevin Oberman" <oberman@es.net> wrote: > > > >2. Building a kernel with config is not officially supported. It's at > > your risk and may not work in all cases. Build a kernel with: > > cd /usr/src > > make buildkernel > > I was not aware that you wern't supposed to use config anymore - and I > am not convinced that the suggested alternative is actually a replacement > as I thought that buildkernel required you to have built the world first ? > Is this no longer true ? If it *is* true thhen what is the alternative to > using 'config' which should be used if you are on a system where you do > not have the time or the disc space to rebuild the world and simply want > to recompile the kernel ? >If you're upgrading or cross-building for a different architecture then you should be using the upgrade path via buildworld/buildkernel. If you're building the kernel on (and for) a system whose binaries match the sources you're attempting to build your kernel from, you are of course free to use the classical "config/make" method. Basically, the upgrade path does the same thing (config/make) but also ensures that the tools (compiler, toolchain, headers, libraries, config(8), etc.) that are used for the kernel build are up-to-date with your sources. Obviously, when you're NOT upgrading and cross building, your installed tools are up-to-date with your sources, and can be used safely, so you can use a classical config/make method. Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060926/7fc86e8a/attachment.pgp
Pete French wrote:>>On Mon, 25 Sep 2006 11:34:42 -0700, "Kevin Oberman" <oberman@es.net> wrote: >> >>2. Building a kernel with config is not officially supported. It's at >> your risk and may not work in all cases. Build a kernel with: >> cd /usr/src >> make buildkernel > > > I was not aware that you wern't supposed to use config anymore - and I > am not convinced that the suggested alternative is actually a replacement > as I thought that buildkernel required you to have built the world first ? > Is this no longer true ? If it *is* true thhen what is the alternative to > using 'config' which should be used if you are on a system where you do > not have the time or the disc space to rebuild the world and simply want > to recompile the kernel ?AFAIK you can use make buildkernel && make installkernel without recompiling whole world if you have system built from same sources. Miroslav Lachman
Make buildkernel KERNCONF=CONFIG Make installkernel KERNCONF=CONFIG This is enough for only compiling kernel and not world and this is the Smartest way according to FreeBSD handbook. -- Thomas Gouverneur Junior UNIX Administrator TI Automotive -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Pete French Sent: mardi 26 septembre 2006 12:24 To: freebsd-stable@freebsd.org Subject: Building a kernel with config ?> On Mon, 25 Sep 2006 11:34:42 -0700, "Kevin Oberman" <oberman@es.net>wrote:> >2. Building a kernel with config is not officially supported. It's at > your risk and may not work in all cases. Build a kernel with: > cd /usr/src > make buildkernelI was not aware that you wern't supposed to use config anymore - and I am not convinced that the suggested alternative is actually a replacement as I thought that buildkernel required you to have built the world first ? Is this no longer true ? If it *is* true thhen what is the alternative to using 'config' which should be used if you are on a system where you do not have the time or the disc space to rebuild the world and simply want to recompile the kernel ? -pete. _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
On Tue, Sep 26, 2006 at 07:42:50PM +0400, George Potapov wrote:> On Tuesday 26 September 2006 19:23, Sean Bryant wrote: > > > Another way you could achieve the same thing is: > > make kernel KERNCONF=KERNNAME > > > > this will combine both steps in to one. > > Also for those who want to omit the KERNCONF step set KERNCONF in > > /etc/make.conf and you can omit the KERNCONF argument. > > But this also does make clean before building so it may be a pain especially > if you change one file or want to add just another driver.In that case you can just add -DNO_CLEAN to the arguments to make to. -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se