From owner-freebsd-current Thu Nov 9 12:24:12 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA05079 for current-outgoing; Thu, 9 Nov 1995 12:24:12 -0800 Received: from aslan.cdrom.com (aslan.cdrom.com [192.216.223.142]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA05062 ; Thu, 9 Nov 1995 12:24:02 -0800 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by aslan.cdrom.com (8.6.12/8.6.9) with SMTP id NAA06512; Thu, 9 Nov 1995 13:22:04 -0800 Message-Id: <199511092122.NAA06512@aslan.cdrom.com> X-Authentication-Warning: aslan.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: Terry Lambert cc: gibbs@freefall.FreeBSD.org (Justin T. Gibbs), current@freebsd.org, hackers@freebsd.org Subject: Re: config, other kernel build tools In-reply-to: Your message of "Thu, 09 Nov 1995 12:56:21 MST." <199511091956.MAA01736@phaeton.artisoft.com> Date: Thu, 09 Nov 1995 13:22:04 -0800 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org Precedence: bulk >I think the code should be in the right location so I can build a >-current kernel on a -stable machine without sacraficing my ability >to build a -stable kernel on the same -stable machine. Its not where the code is, but where it is installed that you are complaining about. Just moving the code wouldn't be enough to fix your problem. Config would not be found in the standard path in this scenario as well. >> >As it is, I have to clobber my existing config program to build a >> >kernel in an alternate source tree. >> >> ?? Doesn't that alternate source tree contain an "arch"/conf directory? >> The compile area is created relative to that directory. > >My existing config *program*, not my existing *config*. Sorry, mis-read that. >/usr/sbin/config is *not* created relative to that directory. > >I *don't* want to toast my existing /usr/sbin/config; I like it, it >is my friend, it serves me well. Than change DESTDIR in your alternate source tree before you do the install. :) >What I'd really like is an incremental step in Richard's planned >mega-makefile patch direction. Putting the tools that are only good >for building kernels in with the kernel code that is to be built is >a good first step. So you advocate is gets installed into the conf dir? Ugh. >It's not like the boot code, etc. isn't already in the kernel tree >and isn't really kernel code proper. The main reason we want to do away with config is that it just isn't flexible enough and we have to hack it all of the time. If config wasn't such a poor utility, there would be nothing wrong with having it in /usr/sbin since it would only change once in a blue moon. > Terry Lambert > terry@lambert.org >--- >Any opinions in this posting are my own and not those of my present >or previous employers. -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations ===========================================