From owner-freebsd-current@FreeBSD.ORG Wed Mar 24 01:31:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CC3F16A4CE; Wed, 24 Mar 2004 01:31:04 -0800 (PST) Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id C305D43D58; Wed, 24 Mar 2004 01:31:03 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (069d2b8b904824e6760c55c29f77af55@adsl-67-119-53-203.dsl.lsan03.pacbell.net [67.119.53.203])i2O9V2bF009044; Wed, 24 Mar 2004 03:31:02 -0600 (CST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 80D3751BB5; Wed, 24 Mar 2004 01:31:01 -0800 (PST) Date: Wed, 24 Mar 2004 01:31:01 -0800 From: Kris Kennaway To: Ruslan Ermilov Message-ID: <20040324093101.GA44928@xor.obsecurity.org> References: <20040324012315.GA40315@xor.obsecurity.org> <20040324065815.GA40963@ip.net.ua> <20040324070256.GA44741@xor.obsecurity.org> <20040324082045.GA41172@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SUOF0GtieIMvvwua" Content-Disposition: inline In-Reply-To: <20040324082045.GA41172@ip.net.ua> User-Agent: Mutt/1.4.2.1i cc: current@FreeBSD.org cc: Kris Kennaway Subject: Re: [FAQ] Prerequisites for a successful buildworld/buildkernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Mar 2004 09:31:04 -0000 --SUOF0GtieIMvvwua Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 24, 2004 at 10:20:45AM +0200, Ruslan Ermilov wrote: > > > Yes, src/sys/ is self-sufficient, except for some tools used during > > > buildkernel, aicasm is one of them. > >=20 > > ...which was the content of my question. So, upgrades (buildworld > > then buildkernel) apparently don't work if you don't have /usr/include > > installed to begin with. > >=20 > Of course not. For a successful buildworld (and buildkernel), > it is required to have a complete and non-broken build system, > as we still build lot of tools using the host toolchain. > - build-tools. These are special small helper applications > that are built and used only during buildworld/buildkernel. > For example, "mkinit" for bin/sh and "aicasm" for the > Adaptec SCSI drivers. By the time we get to building the kernel, we have already built world successfully, and a complete up-to-date toolchain is available (but not yet installed in the default location on the host). The failure case I reported to you occurs at this point; missing db.h will allow the world to build, but kernel builds to fail. In other words there's no need for kernel build tools to fail, because everything they require is available from the output of 'make buildworld'. Whether or not it is difficult to use these in the current FreeBSD build implementation is another matter, but your general "of course not" is missing my specific point. Kris --SUOF0GtieIMvvwua Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAYVVVWry0BWjoQKURAmnVAKDBfykmaBZ4bJJL+ihV/h8FK0QHBgCg7eHO 2yGT5BCIafLSglIAqNOv2YU= =qZwA -----END PGP SIGNATURE----- --SUOF0GtieIMvvwua--