Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Jun 1996 03:20:57 +1000
From:      Bruce Evans <bde@zeta.org.au>
To:        chuckr@Glue.umd.edu, gmarco@masternet.it
Cc:        current@FreeBSD.ORG
Subject:   Re: remote make install
Message-ID:  <199606291720.DAA11936@godzilla.zeta.org.au>

next in thread | raw e-mail | index | archive | help
>> > > install -C -o bin -g bin -m 644 worm/makecdfs.sh /usr/share/examples/worm/mak
>> > ecdfs.sh
>> > > *** Error code 71
>> > 
>> > *shrug* - sorry, I really don't know what to tell you!
>> 
>> You probably don't have the directory worm in your /usr/share/examples

>That was it.  I guess the thing to be learned is, when doing a remote 
>install, it might pay to do a make hierarchy, mk, bootstrap, install, not 
>just a make install.

`make world' makes the hierarchy.  I never use `make world' or `make
hierachy', so I'm used to running mtree or mkdir to when `make install'
falls over.  `install' gives good error messages to show the problem:

$ cd /tmp; touch z; install z /tmp/nonesuch/z
install: mkstemp: /tmp/nonesuch for /tmp/nonesuch/z: No such file or directory

This goes to stderr.  The "*** Error code 71" message from make goes to
stdout and isn't as useful.

Bruce



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606291720.DAA11936>