Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 3 Dec 2002 18:08:09 +0200
From:      Ruslan Ermilov <ru@FreeBSD.ORG>
To:        Andrey Beresovsky <and@rsu.ru>
Cc:        Peter Pentchev <roam@ringlet.net>, hackers@FreeBSD.ORG, Oleg Sharoiko <os@rsu.ru>
Subject:   Re: Need to override KRNLCONFDIR variable in command line of make (file /usr/src/Makefile.inc1).
Message-ID:  <20021203160809.GA37607@sunbay.com>
In-Reply-To: <20021203175208.M611-100000@moon.cc.rsu.ru>
References:  <20021203144918.GJ365@straylight.oblivion.bg> <20021203175208.M611-100000@moon.cc.rsu.ru>

next in thread | previous in thread | raw e-mail | index | archive | help

--RnlQjJ0d97Da+TV1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 03, 2002 at 06:22:42PM +0300, Andrey Beresovsky wrote:
> On Tue, 3 Dec 2002, Peter Pentchev wrote:
>=20
> PP> I was wondering about that when I saw your PR; actually, I think that
> PP> the current FreeBSD kernel building infrastructure is quite sufficient
> PP> for what you want to do, without any more modifications.
> PP>
> PP> Why do you need different source trees and kernel config dirs?  I see=
 no
> PP> problem with keeping all kernel configs for the same version of FreeB=
SD
> PP> in the same src/sys/<arch>/conf/ directory, or at least keeping symli=
nks
> PP> to different files in the same src/sys/<arch>/conf/ directory.
> PP>
> PP> Different source trees - if you have a source tree checked out to use
> PP> for building the kernel, what is stopping you from invoking the
> PP> 'buildkernel' target from the corresponding src/ directory, the one
> PP> directly above the sys/ directory?
>=20
> My project involves automatic or semiautomatic checkouts, updates and
> removals of source trees. It would be unwise to keep kernel configs in th=
is
> source trees. Thats why I need to change KRNLCONFDIR variable. Of course,=
 I
> can do it with the help of links, but I think it's not a good solution.
>=20
> I guess the changes I suggest will definitely not break anything but only=
 add
> flexibility which is typical for BSD make files.
>=20
> The solution with links is not a right thing, because it involves more di=
rty
> work which can be avoided with a help of simple makefile modification.
>=20
KRNLCONFDIR shouldn't be overridden -- we already provide (undocumented)
user-redefineable KERNCONFDIR which should be used in cases like this.
KRNLCONFDIR, on the other hand, is dependent on src/ used, and should
NOT be overridden.


Cheers,
--=20
Ruslan Ermilov		Sysadmin and DBA,
ru@sunbay.com		Sunbay Software AG,
ru@FreeBSD.org		FreeBSD committer,
+380.652.512.251	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age

--RnlQjJ0d97Da+TV1
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE97NbpUkv4P6juNwoRAlz5AJwI8FrvwKuLTzDIoSPcoOK4CeOJVwCeOKWJ
ppgNnFdr1afwD2IrPoknPYo=
=vPQL
-----END PGP SIGNATURE-----

--RnlQjJ0d97Da+TV1--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021203160809.GA37607>