Date: Tue, 4 Apr 1995 11:58:51 -0600 From: Nate Williams <nate@trout.sri.MT.net> To: rkw@dataplex.net (Richard Wackerbarth) Cc: current@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/conf Makefile.i386 Message-ID: <199504041758.LAA06600@trout.sri.MT.net> In-Reply-To: rkw@dataplex.net (Richard Wackerbarth) "Re: cvs commit: src/sys/i386/conf Makefile.i386" (Apr 4, 12:33pm)
next in thread | raw e-mail | index | archive | help
> >But, *IF* both the src dist and /usr/include directories exist, the > >include files are pulled out of /usr/src/include if they exist and > >/usr/include next. (Which should never happen since /usr/src/include > >should always contain all of the necessary include files which aren't in > >the /usr/src/sys tree) > > I think that this is bogus behavior. > > If a file is missing from /usr/src/include, I don't want it to be > "magically" found. First of all, there are only two include files that are used that aren't in /usr/src/sys (for the genassym program and for one source file), so it's not a critical problem, and second of all if you don't want to worry about /usr/include stuff being picked up, do a 'mv /usr/include /usr/include.old' before building your kernel. This is more work for you, but penalizing you (minority) is much better than penalizing most folks who want to download the kernel sources and built custom kernels. > Under your scheme, I will never be able to test a > distribution tree for completeness on my production system. Okay, show me a better solution which doesn't *require* that people have /usr/src/include exist and that doesn't require a lot of work for the release engineer. > Further, a user who does not have the entire source distribution could > "create" the includes by either copying or linking in /usr/include. *BLECH* BSD systems have *never* (and should *never*) require that you have the complete source tree installed just to build a kernel. Making them go through alot of trouble to build a kernel is a waste of their time. Many, many more people build kernels w/out src trees than people who build kernels w/src trees. We are trying to make the system *easier* to use for the avg. user w/out penalizing the developer. Show me a solution that does that and it'll get into the tree. If it doesn't provide both, then it's not a complete solution. I wanted to provide a ENVIRONMENT variable which was set to provide /usr/src/include protection, but it was show down. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504041758.LAA06600>