From owner-cvs-all Tue Jan 23 12:30:40 2001 Delivered-To: cvs-all@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 2276A37B400; Tue, 23 Jan 2001 12:30:16 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0NKU6t24964; Tue, 23 Jan 2001 12:30:06 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: Gerhard Sittig Cc: "Jordan K. Hubbard" , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src Makefile.inc1 In-Reply-To: Message from Gerhard Sittig of "Tue, 23 Jan 2001 19:55:31 +0100." <20010123195531.G253@speedy.gsinet> Date: Tue, 23 Jan 2001 12:30:06 -0800 Message-ID: <24959.980281806@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Without knowing much more specifically what you mean by "config(8) output reporting", it's impossible to answer this question. It could either be unwonted noise or useful information, depending on just how much and of what nature this information is. My gut reaction is that config(8) shouldn't say anything unless you ask it to, however, and there are already provisions made for passing in CONFIGARGS so if you wanted to add a -v flag, that might fly without too much contraversy. - Jordan > On Mon, Jan 22, 2001 at 15:26 -0800, Jordan K. Hubbard wrote: > > jkh 2001/01/22 15:26:19 PST > > > > Modified files: (Branch: RELENG_4) > > . Makefile.inc1 > > Log: > > MFC: kernel time reporting. > > Is there a need for config(8) output reporting? That's what I'm > asking myself from reading the latest thread on the subject. > > Although buildkernel is the "official" method of building a > kernel, it is said to suffer from information hiding. Will > collecting and summarizing config(8)'s output be easier than > converting all warnings to errors or not suggesting to use the > buildkernel target any longer? > > I'm aware that there's not much point in building with a maybe > damaged or dangerous configuration and reporting the problem > afterwards. And admittedly I'm absolutely ignorant when it comes > to the tool chain and build process. But I thought this could be > a quick way of providing the information and yet stick with the > convenient and officially supported target and have the best of > both worlds until a better solution becomes available. > > > virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 > Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net > -- > If you don't understand or are scared by any of the above > ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message