Subject: bin/1901: utility programs in /usr/src/domestic built inconsistently (at best)
To: None <gnats-bugs@gnats.netbsd.org>
From: Chris G. Demetriou <cgd@NetBSD.ORG>
List: netbsd-bugs
Date: 01/06/1996 01:35:17
>Number:         1901
>Category:       bin
>Synopsis:       build of domestic utilities is haphazard & inconsistent
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jan  6 01:50:05 1996
>Last-Modified:
>Originator:     Chris G. Demetriou
>Organization:
Kernel Hackers 'r' Us
>Release:        NetBSD-current, January 5, 1996
>Environment:
	
System: NetBSD sun-lamp.pc.cs.cmu.edu 1.1A NetBSD 1.1A (SUN_LAMP) #19: Thu Jan 4 20:42:03 EST 1996 cgd@sun-lamp.pc.cs.cmu.edu:/usr/src/sys/arch/i386/compile/SUN_LAMP i386


>Description:
	The way /usr/src/domestic 'build utilities,' i.e. programs
	used while building the libaries and programs, are built is
	inconsistent and haphazard.

	For instance during the build process for /usr/src/domestic:
		(1) if 'make_cmds' isn't built yet, nothing will build
		    it, but
		(2) before 'compile_et' is used, Makefiles cd into its
		    directory and try to 'make depend && make'

	This results in compiles failing, if make_cmds isn't built before
	a build in another directory (e.g. lib/libss) is run.

	It also results in the Makefiles trying to build 'compile_et'
	three or four times over the course of a /usr/src/domestic build.

	These two should at least be consistent.

>How-To-Repeat:
	When /usr/src/domestic/usr.bin/make_cmds hasn't been built,
	cd into /usr/src/domestic/lib/libss and try to make
	(and note that the make fails, in part due to the fact that
	no make_cmds binary can be found).

	Note that each of lib/{libkadm,libkrb,libss} each will try
	to build 'compile_et' before they try to use it.

	Note that these two behaviours aren't consistent, and that the
	'compile_et' behaviour is a bit wasteful.

>Fix:
	Pick the 'right' way to do utility builds, and implement it
	consistently in the various places where utility programs
	are used.
>Audit-Trail:
>Unformatted: