From owner-freebsd-current Thu Sep 30 14: 9:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id F04B915143 for ; Thu, 30 Sep 1999 14:08:51 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA24331; Thu, 30 Sep 1999 14:08:29 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199909302108.OAA24331@gndrsh.dnsmgr.net> Subject: Re: new sigset_t and upgrading: a proposal In-Reply-To: from Bruce Evans at "Oct 1, 1999 06:22:57 am" To: bde@zeta.org.au (Bruce Evans) Date: Thu, 30 Sep 1999 14:08:28 -0700 (PDT) Cc: marcel@scc.nl (Marcel Moolenaar), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Why are the tools being built using new syscalls? What causes this? > > Mainly historical bugs. Includes are installed too early and they only > match the new syscalls. Tools are built using the new includes, so they > need new libraries to be consistent. Therefore the new libraries are > built before the new tools. These bugs were implemented in FreeBSD-1 by > someone named rgrimes :-). I'll eat the crow, yes, I did implement that. It was the first step at even being able to ``make world''. Had to start some place. And technically the bug dates back to the patchkit, infact probably a 1.x version of the 386BSD PatchKit. Now, the addition of obj/tmp and the TOOLS thing was suppose to fix that by using the current headers/libraries to build a set of tools that didn't go smashing around on the system. If someone copied the earlier work that had a different purpose, and these nasty bugs, well... they would certainly still be there! -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message