Ok, let's assume for now that something was wrong with the makefile or
there was a glitch in the make/install process.
(I have only updated once before so I have never had to recover from
something like this.)
Would it be ok to simply repeat the entire process, minus the cvsup part?
Is it also possible that I answered some questions wrong in the first
'mergemaster -p' go through?
Should I also .... before I start ....
Luke Dean wrote:
On Wed, 10 May 2006, bc wrote:
Ceri Davies wrote:
Now that I am in front of the derver here is the full message (with a
few lines before) pasted:
On 10/5/06 05:03, "bc" <[EMAIL PROTECTED]> wrote:
After make installworld I ran the final run thru of mergemaster and
ERROR CODE 64
FATAL ERROR: Cannot 'dc' into /usr/src/etc/ and install files to the
Did you cut and paste that, or copy it in manually?
install -o root -g wheel -m 640 /dev/null
install -o root -g wheel -m 644 freebsd.cf
install -o root -g wheel -m 444 freebsd.submit.cf
cd /usr/src/etc; install -o root -g wheel -m 644
usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
[-o owner] file1 file2
install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
[-o owner] file1 ... fileN directory
install -d [-v] [-g group] [-m mode] [-o owner] directory ...
*** Error code 64
Stop in /usr/src/etc.
*** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to
the temproot environment
/usr/src Walnut SuperUser#>
"install" is being run with a blank space where the program name
should be. That's what it's complaining about. It does not look like
a directory problem or a permissions problem.
I'd say that something is wrong with a makefile that builds ssh or
with your "make" configuration.
I'm afraid I don't know enough about the "make" process to say more
than that, but perhaps if you can specify which platform you're
building for and the contents of /etc/make.conf somebody more
knowledgable might be able to help.
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"