Date: Wed, 22 Feb 1995 21:12:22 -0800 From: David Greenman <davidg@Root.COM> To: Garrett Wollman <wollman@halloran-eldar.lcs.mit.edu> Cc: Poul-Henning Kamp <phk@ref.tfs.com>, current@freefall.cdrom.com Subject: Re: TRUE and FALSE Message-ID: <199502230512.VAA00806@corbin.Root.COM> In-Reply-To: Your message of "Wed, 22 Feb 95 17:27:14 EST." <9502222227.AA08707@halloran-eldar.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
><<On Wed, 22 Feb 1995 14:23:59 -0800 (PST), Poul-Henning Kamp <phk@ref.tfs.com> said: > >> If you develop kernel-dependent sw, you had better make sure that your >> development env is aligned with your kernel, ie something like: > >> cd /usr/src/include ; make all install >> cd /usr/src/sys ; make all install > >> or whatever the trick will be. > >And I'm saying that it's an incredible imposition to force such >developers to do this every time they make a change to a kernel header >file. I won't stand for it. Neither will I. It's a recipe for new and interesting bugs. If the problem with the symlinks should be fixed at all, it should be made so that each header has it's own symlink in /usr/include/sys/*. These can still indirect through /sys to make it easy to reassign the whole thing (/usr/include/sys becomes a directory with symlinks to the headers in /sys/*). -DG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199502230512.VAA00806>