Date: Fri, 29 Sep 1995 12:55:51 -0700 From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org> To: John Capo <jc@irbs.com> Cc: gibbs@freefall.freebsd.org (Justin T. Gibbs), ache@freefall.freebsd.org, CVS-commiters@freefall.freebsd.org, cvs-sbin@freefall.freebsd.org Subject: Re: cvs commit: src/sbin Makefile Message-ID: <199509291955.MAA24827@aslan.cdrom.com> In-Reply-To: Your message of "Fri, 29 Sep 1995 15:45:45 EDT." <199509291945.PAA27305@irbs.irbs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>Justin T. Gibbs writes: >> >> >ache 95/09/29 12:35:11 >> > >> > Modified: sbin Makefile >> > Log: >> > Build secure init if available and allowed >> >> On a similar subject, shouldn't "MAKE_EBONES" go away? Shouldn't the >> build be based solely on the existance of the directory? > >That's the way it used to work. Some of us build different >configurations from the same source tree. It was a pain to move >the directory out of the way and then back. What's the use of most of what is in secure without a built eBones? In fact our secure telnet did absolutely nothing for us until it was recently fixed to work with eBones. Yet, many makefiles use the "MAKE_EBONES" variable to make decisions on how to build things. If anything, there sould be a single variable referenced in /usr/src/Makefile for non exportable material that simply exludes the right subdirectories. > >John Capo >IRBS Engineering -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations ===========================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509291955.MAA24827>