Subject: Re: Can't create i386 installation floppies under -current
To: None <earle@isolar.Tujunga.CA.US>
From: Mike Long <mike.long@analog.com>
List: current-users
Date: 05/01/1996 11:17:31
>Date: Tue, 30 Apr 1996 12:04:34 -0700
>From: Greg Earle <earle@isolar.Tujunga.CA.US>

>scipio# pwd
>/usr/src/distrib/i386/floppies
>
>scipio# make
>===> inst
>crunchgen -D /usr/src/distrib/i386/floppies/inst/../../../.. -L /usr/lib \
>/usr/src/distrib/i386/floppies/inst/../inst-common/instbin.conf
>/usr/src/distrib/i386/floppies/inst/../inst-common/instbin.conf: fsck: warning:
>could not find source directory.

distrib/i386/inst-common/instbin.conf wasn't updated after fsck was
renamed to fsck_ffs.

>This created "instbin.c", "instbin.mk" and "instbin.cache" in the "inst"
>sub-directory, but that was it.  I then cd'ed down into "inst" and did the
>"make -f instbin.mk objs exe" as directed, and it successfully made "instbin".

...except that fsck is missing.

>scipio# make
>crunchgen -D /usr/src/distrib/i386/floppies/kcadp/../../../.. -L /usr/lib \
>/usr/src/distrib/i386/floppies/kcadp/../kc-common/kcbin.conf
>/usr/src/distrib/i386/floppies/kcadp/../kc-common/kcbin.conf: fsck: warning:
>could not find source directory.

distrib/i386/kc-common/kcbin.conf also needs an update.

>Again, I did the requisite "make -f kcbin.mk objs exe" and it created "kcbin"
>just fine.

...except fsck is missing here, too.

>disklabel -w -B -b /usr/mdec/fdboot -s /usr/mdec/bootfd vnd0 floppy5
>ioctl DIOCWLABEL: Inappropriate ioctl for device
>ioctl DIOCWLABEL: Inappropriate ioctl for device
>
>(These can be ignored, I presume)

Yup.  /dev/vnd* doesn't grok DIOCWLABEL.

>COPY    ${CURDIR}/../../../../sys/arch/i386/compile/INSTADP/netbsd      netbsd
>cp: /usr/src/distrib/i386/floppies/kcadp/../../../../sys/arch/i386/compile/INSTADP/netbsd: No such file or directory
>*** Error code 1
>
>Stop.
>
>(Is there a way to introduce a Makefile dependancy that checks to see whether
> the directory "${CURDIR}/../../../../sys/arch/i386/compile/INSTADP" exists?)

Yes, is it worth the effort?  You get the error message the first time
(as I did) and then you know what to do.
-- 
Mike Long <mike.long@analog.com>     <URL:http://www.shore.net/~mikel>
VLSI Design Engineer         finger mikel@shore.net for PGP public key
Analog Devices, CPD Division          CCBF225E7D3F7ECB2C8F7ABB15D9BE7B
Norwood, MA 02062 USA       (eq (opinion 'ADI) (opinion 'mike)) -> nil