Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!uunet!stanford.edu!cascade.stanford.edu!cascade!interran From: interran@lurch.Stanford.EDU (John Interrante) Newsgroups: comp.windows.interviews Subject: Re: Installation Report 3.0-beta Message-ID: Date: 28 Apr 91 03:32:16 GMT References: <3429@kluge.fiu.edu> Sender: news@cascade.Stanford.EDU (USENET News System) Organization: Stanford University Lines: 29 In-Reply-To: ege@scs.fiu.edu's message of 27 Apr 91 14:28:50 GMT In article <3429@kluge.fiu.edu> ege@scs.fiu.edu (Raimund K. Ege) writes: During installation we encountered a minor problem for the script files: + install -c -m 0755 cpu ../../.././installed/bin/SUN4 cp: 0755: No such file or directory chmod: ../../.././installed/bin/SUN4/0755: No such file or directory I never saw this problem before, but I can guess what happened. It was a combination of three mistakes, two ours and one yours: 1) We had an executable script called `install' in src/bin/scripts. 2) You had `.' ahead of /usr/bin in your PATH. 3) The script had a bug in it. We should never have had an executable script called install in src/bin/scripts, but we weren't careful enough when we made the 3.0-beta snapshot. When you tried to install the script files, make invoked src/bin/scripts/install instead of /usr/bin/install because you had `.' ahead of /usr/bin in your PATH. The script was very old (it came from X11R3), so it had a bug which caused the error messages you saw. You should delete src/bin/scripts/install and you should put `.' last in your PATH to make sure you don't accidentally invoke an executable file in the current directory again because it has the same name as a command. -- John Interrante / interran@lurch.stanford.edu