>Number:         8297
>Category:       install
>Synopsis:       Can't build install floppy on 1.4.1+release
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    install-manager (NetBSD system installation bug manager)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 31 03:50:01 1999
>Last-Modified:
>Originator:     Frederick Bruckman
>Organization:
	
>Release:        sup of "release", Aug 30, 1999
>Environment:
	
System: NetBSD handy.localnet 1.4.1 NetBSD 1.4.1 (HANDY) #6:
Tue Aug 31 02:39:07 CDT 1999
root@handy.localnet:/usr/src/sys/arch/i386/compile/HANDY i386


>Description:
	
	Besides the fact the "make" in /usr/src/distrib doesn't
	even try to build a ramdisk, "cd /usr/src/distrib; make;
	cd /usr/src/distrib/i386/floppies; make" fails as follows:

(cd /usr/src/distrib/i386/floppies/ramdisk/../../../../usr.sbin/mbrlabel; make m
brlabel.o dkcksum.o)
`mbrlabel.o' is up to date.
`dkcksum.o' is up to date.
cc -static -o ramdiskbin ramdiskbin.o bad144.lo cat.lo chmod.lo chown.lo chroot.
lo cp.lo dd.lo df.lo disklabel.lo ed.lo fsck.lo fsck_ffs.lo ftp.lo gzip.lo ifcon
fig.lo init.lo installboot.lo less.lo ln.lo ls.lo mkdir.lo mknod.lo mount.lo mou
nt_cd9660.lo mount_ext2fs.lo mount_ffs.lo mount_msdos.lo mount_nfs.lo mount_kern
fs.lo mt.lo mv.lo newfs.lo ping.lo pwd.lo reboot.lo restore.lo rm.lo route.lo se
d.lo sh.lo shutdown.lo slattach.lo stty.lo swapctl.lo sync.lo test.lo tip.lo umo
unt.lo update.lo sysinst.lo pax.lo fdisk.lo mbrlabel.lo -L/usr/lib  libhack.o -l
edit -lutil -lcurses -ltermcap -lrmt -lcrypt -ll -lm
cc: libhack.o: No such file or directory
*** Error code 1

Stop.
*** Error code 1

Stop.

But

root% make libhack.o
`libhack.o' is up to date.

?!

>How-To-Repeat:
	
	As above. 
>Fix:
	
	Wish I knew. There are so many levels of "includes" and
	"Makefile.inc"'s that it's almost impossible to follow.

	I feel strongly that "cd /usr/src/distrib; make
	RELEASE=/usr/Release release" should, at the very least,
	make and install the root of the release under /usr/Release,
	i.e.  run "mtree" under /usr/Release, and build and install
	the notes and the install floppies there, too. Even nicer
	would be a "distrib target", that depends on "release",
	then does

	(cd ../src; make EXPORTABLE_SYSTEM= release)
	(cd ../xsrc; make build && make release)
	(cd ../src/${CRYPTO}; make release)

	filling in the missing pieces, as required.



>Audit-Trail:
>Unformatted: