From owner-freebsd-current Tue Apr 4 15:50:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA25238 for current-outgoing; Tue, 4 Apr 1995 15:50:35 -0700 Received: from mail.barrnet.net (mail.BARRNET.NET [131.119.246.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA25232 for ; Tue, 4 Apr 1995 15:50:34 -0700 Received: from dataplex.net (SHARK.DATAPLEX.NET [199.183.109.241]) by mail.barrnet.net (8.6.10/MAIL-RELAY-LEN) with ESMTP id PAA20031 for ; Tue, 4 Apr 1995 15:47:39 -0700 Received: from [199.183.109.242] by dataplex.net with SMTP (MailShare 1.0b8); Tue, 4 Apr 1995 17:49:54 -0500 X-Sender: wacky@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 4 Apr 1995 17:49:56 -0500 To: current@FreeBSD.org, rgrimes@gndrsh.aac.dev.com, nate@trout.sri.MT.net From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: cvs commit: src/sys/i386/conf Makefile.i386 Sender: current-owner@FreeBSD.org Precedence: bulk Rodney Grimes writes: >You are missing a very important fact about genassym, it *IS* heavly >dependent upon the kernel configuration file. Your not going to be able >to make a version of the binary genassym that will work for all kernel >builds. It must be built and run on the ``hosted'' system, it is >meaningless to build a ``targeted'' system version of it. But the same could be said about any "tool" used to make a kernel. I see absolutely no reason why you should treat the correct production of a genassym that ends up on the target machine any differently from say gcc. I should be able to precompile EVERYTHING and then recompile ONLY those elements that depend on something that has changed. So maybe that means that genassym gets recompiled almost anytime I change the kernel. Maybe it doesn't. "Make" should properly take care of it in either case. There should not be a special case for this one tool. ---- Richard Wackerbarth rkw@dataplex.net